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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint, so the description doesn't need to restate safety. The description adds the 'curated' aspect, which is a behavioral trait (pre-selected vs. exhaustive results), but doesn't disclose return format or other behaviors like pagination. With the annotation coverage, this is adequate but not rich.

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 compact and front-loaded with the purpose in the first sentence. The trigger list is clearly structured and directly useful for usage decisions. Every sentence earns its place — no filler or redundant details.

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?

With two parameters, one enum, full schema coverage, and helpful annotations, the description is largely complete for a simple browse operation. It doesn't describe return values, which could be a gap without an output schema, but the tool's simplicity and direct language make it clear enough for an agent to use correctly.

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 schema provides complete parameter descriptions (100% coverage), but the description adds value by mapping natural language trigger phrases to the theme enum values (e.g., 'date night' → 'date-night'). This helps the agent select the correct parameter value beyond what the schema alone offers, even though the limit parameter isn't elaborated further.

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 tool's function with a specific verb ('Browse') and resource ('curated recipe collections by theme'). It distinguishes this from sibling recipe tools by emphasizing curated collections rather than search or individual retrieval, and the trigger examples make the scope immediately understandable.

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?

Provides explicit trigger phrases that indicate when to use this tool, such as 'date night recipes' and 'comfort food ideas'. While it doesn't name specific alternatives or exclusions, these triggers effectively guide an agent on when this tool is appropriate, especially compared to broader search tools like recipes_search.

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