Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With annotations only declaring this a non-idempotent, non-destructive write, the description adds substantial behavioral context: starring subscribes the user to job postings, unlocks the full tech stack, is free and consumes no budget, and is subject to a limited number of active star slots reported by get_account. This goes well beyond the structured fields.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loads the core action and effects before the CRITICAL guidance, and every clause carries meaning. It is on the long side and the tech-stack-overlap warning is somewhat repetitive, but not padded.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

No output schema exists, and the description still tells the agent what happens as a result (jobs appear in get_starred_jobs, tech stack unlocks, slots are consumed and tracked via get_account). Nothing needed to invoke it correctly is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% for the single listingId parameter, so the schema already documents its format. The description adds decision-relevant context about how to judge candidates (use matchedTechStack, not the visible preview) but nothing about the parameter itself, so the baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb+resource ('Star/save a company listing') and immediately distinguishes it from its sibling unstar_listing by describing the state change and its consequences. The agent can tell exactly what operation is being performed.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives explicit when-to-use criteria ('Only star companies where the user's tech stack genuinely overlaps'), a concrete counter-example (React/Node developer should NOT star a Go/Java-only company), and names alternatives/related tools (get_starred_jobs, get_account, search_listings). This is unusually rich routing guidance.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.