remove_favorite

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

No annotations provided; description only states authentication requirement but omits idempotency, error handling, or side effects.

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 with no wasted text. Front-loaded with purpose and auth hint.

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?

Has output schema, so return values need not be described. However, lacks behavioral context like idempotency or error behavior for a simple removal tool.

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?

Parameter description merely restates the schema field name ('restaurant ID to unfavorite') without adding format, source, or constraints. Schema coverage 0% magnifies the gap.

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?

Clear verb ('remove') and resource ('restaurant from favorites') are stated. Distinguishes from sibling add_favorite.

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?

Briefly notes AUTH'D, but no explicit when-to-use or alternatives. Context suggests it complements add_favorite, but not stated.

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