my_recipes

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

No annotations are supplied, so the description carries the full burden; it does disclose the login requirement, which is genuinely useful preconditions information. It says nothing about whether the call is read-only, how results are ordered or paginated, or what happens when the user has no favourites.

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 no filler, and the resource statement is front-loaded. It is terse rather than padded, though brevity here shades into under-specification.

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 needn't be explained, but the description still omits what a "favourite recipe" record is, how it relates to the favourites and recipe siblings, and what limit does. For a tool with no annotations and zero schema coverage, this leaves the agent guessing.

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 never mentions the single limit parameter or its default of 20. An agent must open the schema to learn the parameter exists and gets no semantic guidance on what limit bounds.

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?

"Your favourite recipes" names the resource but gives no verb, so it's ambiguous whether the tool lists, fetches, or filters recipes. It also doesn't distinguish itself from the sibling favourites or search_recipes/recipes_by_category 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?

The only guidance is "Requires login" — an auth prerequisite rather than a usage condition. Nothing says when to call this instead of favourites, my_products, search_recipes, or recipes_by_category.

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