Unstar Company

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

Description discloses that unstarring consumes from an unstar budget per billing period, preventing unlimited cycling. This adds value beyond annotations (destructiveHint, idempotentHint) by explaining the side effect and precondition.

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?

Extremely concise: two informative sentences plus a warning. No unnecessary words or repetition.

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?

Complete for a simple tool with one parameter and no output schema. Explains effect, side effects, and precondition. Could mention return value or error conditions, but not required.

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 covers 100% of the single parameter with clear description and regex pattern. The tool description does not add further parameter details, but baseline is acceptable given high schema coverage.

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?

The description clearly states the action 'Remove a star from a company listing', using a specific verb and resource. It distinguishes from sibling tools like 'star_listing' and 'get_starred_listings'.

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?

Explicit guidance is given: check remaining unstar budget via get_star_count before use, and only unstar if truly not relevant. No explicit when-not-to-use, but the budget constraint implies careful usage.

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