add_favorite

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

No annotations are provided, so the description carries the full behavioral burden. It discloses the authentication requirement, which is a plus, but says nothing about idempotency, what happens if the restaurant is already favorited, or error behavior for an invalid ID.

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?

Two short sentences with the core action front-loaded and the auth prerequisite immediately after. The trailing 'Args:' block is slightly redundant with the schema but is compact enough not to hurt readability.

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?

An output schema exists, so return values need not be explained, and the tool is a single-parameter mutation. Still missing is how to obtain a valid restaurant_id and what happens on duplicate favorites, which would matter for correct invocation.

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 description coverage is 0%, so the description must carry the parameter burden. Instead it only restates the field name ('The restaurant ID to favorite'), adding no source, format, or example for obtaining restaurant_id, which matters given siblings like search_restaurants and get_restaurant.

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 and resource: 'Add a restaurant to favorites'. An agent can identify the action immediately, but the description never names the sibling remove_favorite or otherwise distinguishes itself from adjacent favorites tools.

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?

'Requires authentication' is a useful prerequisite, implicitly telling the agent a session must exist before calling. However, there is no guidance on when to prefer this over related tools like get_favorites or remove_favorite, so usage context is only implied.

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