list_shared_recipes

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

The description adds no behavioral context beyond the name. With no annotations, the agent cannot infer read-only nature, authentication needs, or rate limits. The phrase 'Get All' does not disclose any traits.

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?

While short, the description is under-specified. It uses only two words but provides negligible value, lacking essential details that would justify its brevity.

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?

Given the presence of many sibling list tools and optional parameters, the description is severely incomplete. It fails to explain the scope of results, filtering behavior, or output structure, even though an output schema exists.

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 zero description coverage (0%). The description does not mention parameters like recipe_id (for filtering) or accept-language (for localization), leaving their meaning entirely to the schema's property definitions.

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 'Get All' is a tautology that merely restates the action implied by the name 'list_shared_recipes'. It does not specify the resource being listed with a specific verb, nor does it differentiate from sibling tools like list_recipes or get_shared_recipes_by_item.

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?

No guidelines provided. There is no indication of when to use this tool versus alternatives (e.g., get_shared_recipes_by_item, list_recipes). The description lacks context on prerequisites, filtering, or pagination.

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