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

With no annotations, the description carries the full burden and does so thoroughly: it discloses that the tool is free, that every request is catalogued to inform future data builds, that nothing identifying is stored, and that the response includes availability plus the MCP endpoint when available. This goes well beyond typical 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?

Every sentence earns its place: cost, action and outcome, scope expansion, cataloging, and privacy. The free note is front-loaded, and there is no redundant or filler wording.

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 single-parameter tool with no output schema and no annotations, the description covers cost, input flexibility, the nature of the response, and data handling. The 'get back whether... with the MCP endpoint if so' statement sufficiently implies the response format, and a simple yes/no with optional endpoint is enough for this use case.

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% with a clear description and example for the 'need' parameter. The description adds only modest guidance ('in your own words', 'anything, not just food') on top of the schema, so it stays at the baseline for a fully covered schema.

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 (describe) and resource (the data you are trying to buy), with a clear outcome: get back whether the service supplies it and the MCP endpoint if so. It also explicitly broadens scope beyond food, making it easy to distinguish from the food-focused sibling 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?

Provides clear context for when to use this tool: when you have a data need to describe and want to know if the service can supply it, including non-food data. It does not explicitly name alternatives or state when not to use it, but the 'anything, not just food' phrasing is a helpful differentiation signal.

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