List Shared Recipes

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

No annotations are present, so the description carries the full burden of behavioral disclosure. 'Get All' only vaguely implies retrieval and reveals nothing about whether the operation is read-only, whether it returns only shared recipes, how optional parameters affect behavior, or what authentication or error semantics apply.

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?

The description is extremely short, but this is under-specification rather than effective conciseness. A two-word phrase cannot carry enough meaning for an agent to invoke the tool correctly.

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 two optional parameters, no annotations, and a large sibling set with related shared-recipe tools, the description is completely inadequate. An agent cannot determine the tool's scope, filtering behavior, localization handling, or relationship to other endpoints.

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% and the description does not mention recipe_id or accept-language at all. The agent cannot determine whether recipe_id filters results, whether accept-language controls localized output, or how these optional parameters interact.

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 is only 'Get All', a generic fragment that does not name a specific resource or behavior. It adds no value over the title 'List Shared Recipes' and does not distinguish this from siblings like get_shared_recipes_by_item or list_recipes.

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?

There is no guidance about when to use this tool versus alternatives. It does not mention filtering, scoping, pagination, or any condition that would lead an agent to select this tool over list_recipes or get_shared_recipes_by_item.

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