resy_remove_favorite

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

No annotations are provided, so the description bears full responsibility for disclosing behavior. It only states the removal action, but does not mention side effects (e.g., irreversible), required user authentication, or behavior when the venue is not already a favorite. This lacks critical context for an AI agent.

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?

A single sentence with 10 words, no redundancy. Every word is informative and directly describes the tool's purpose.

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?

For a simple removal tool with one required parameter, the description is minimally sufficient. However, it omits details like whether removal is permanent, whether the venue must exist in favorites, or what the return behavior is (e.g., success indication). Given no output schema, these are gaps.

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?

The input schema has 0% description coverage, meaning the description must compensate. However, the description only mentions 'by venue_id' and adds no deeper semantics (e.g., format, origin, or constraints) beyond what the schema already provides. The parameter name is not sufficiently explained.

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 uses specific verb 'Remove' and resource 'venue from the user's favorites', with the parameter 'by venue_id'. This clearly differentiates from the sibling 'resy_add_favorite' and leaves no ambiguity about what the tool does.

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?

The description implicitly suggests when to use the tool (when removing a favorite), but it does not explicitly state when not to use it or mention alternatives like 'resy_add_favorite'. For a simple opposite operation, the context is adequate but not explicit.

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