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, yet it says nothing about pagination or how 'limit' defaults, result ordering, or whether filtering is conjunctive. It also doesn't disclose auth or rate-limit characteristics. Given zero annotation coverage for a 7-parameter listing tool, this is a thin disclosure.

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?

A single front-loaded sentence with no filler, which is structurally clean. It is arguably underspecified rather than wasteful, so the terse form costs a little clarity without bloating.

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 7-parameter, zero-required, zero-coverage listing tool with no annotations, the description omits nearly everything an agent needs to call it correctly. The presence of an output schema means return values needn't be described, but filter semantics, limit behavior, and sibling routing are all missing.

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 all seven parameters (tags, agent, limit, facets, section, severity, min_quality) are undocumented anywhere. The phrase 'metadata filtering' gestures at the filter family but gives no semantics for any individual parameter or how they combine.

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 ('List recipes') plus a scope qualifier ('optional metadata filtering'), so the basic operation is clear. However, it does nothing to distinguish itself from siblings like recipes_search or recipes_get, which a listing tool must do since an agent choosing between them has no signal here.

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 guidance on when to use this versus recipes_search (query-based retrieval) or recipes_get (single-item lookup). There are also no prerequisites or exclusions, so the agent must infer the routing entirely from the name.

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