get_favorite_recipes

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

Annotations already indicate readOnlyHint and idempotentHint, but the description adds the critical behavioral detail that authentication is required. This goes beyond the structured data and informs the agent of a necessary 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?

Two efficient sentences: the first delivers the core purpose, the second provides a critical usage instruction. Every sentence earns its place with no wasted words.

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 zero-parameter, read-only tool with no output schema, the description is adequate. It states the resource, owner, and auth requirement. The return format could be hinted, but given sibling tools and common knowledge, this is a minor gap.

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?

There are no parameters (input schema is empty), so schema coverage is 100% trivially. The description adds no parameter details, but none are needed. The focus on what the tool returns (user's favorites) provides context beyond the empty schema.

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 ('Get') and the resource ('the user's favorite recipes'). This distinctively sets it apart from siblings like search_recipes (search all recipes) and get_recipe (single recipe by ID), and from add/delete_favorite_recipe.

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 explicitly names a prerequisite (profile auth) and recommends an action (check_auth_status first). While it does not specify when to avoid this tool or list full alternatives, the context is clear and directive.

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