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

Beyond the readOnlyHint annotation, the description discloses meaningful behavior: the hybrid dense + ColBERT retrieval, the compact hit shape {id,title,cuisine,dietary,cookbook}, the up-to-limit cap, and the hidden trap that many recipes are unlabelled and only reachable via concept search. This is valuable context that the annotation alone does not provide.

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 dense but every sentence earns its place: purpose, method, examples, return shape, iteration guidance, and a critical warning. It is front-loaded with the primary action and does not waste words on redundant filler.

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 tool's moderate complexity, full parameter schema coverage, and read-only annotation, the description is complete. It explains the expected output shape despite the lack of an output schema, gives rich query guidance, and provides clear call/re-call behavior, leaving no critical gap for an agent deciding how to invoke it.

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 coverage is 100%, so the baseline is 3. The description adds real semantic value for the query parameter by insisting on a rich natural-language concept over a keyword and providing concrete examples such as 'cozy cold-weather baked desserts.' The limit parameter also gains context from the phrase 'Returns up to limit compact hits.'

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 opens with a specific action and resource: 'Search the recipe collection semantically (dense + ColBERT hybrid) to gather the members of a theme.' This clearly distinguishes it from siblings like get_recipe or lookup_cuisine, and the purpose—retrieving theme members via concept search—is explicit.

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?

It gives concrete when-to-use direction: gather theme members, pass a rich concept rather than a keyword, call once per concept, and adjust the query if results are too small or too large. It also warns against relying on cuisine labels because many recipes are unlabelled, effectively steering the agent away from sibling tools like lookup_cuisine.

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