agriculture-mcp-server

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

Discloses return data (Nährwerte, Nutri-Score, Eco-Score, NOVA-Gruppe) and data source (Open Food Facts) despite no annotations or output schema.

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?

Well-structured with purpose, return value, source, and args sections; every sentence adds value; appropriately brief.

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?

Explains return values comprehensively given lack of output schema; single parameter is adequately documented.

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?

Compensates for 0% schema description coverage by specifying format (EAN/UPC) and concrete example (Nutella barcode).

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?

Specific verb+resource ('Lebensmittel per Barcode nachschlagen') clearly distinguishes from sibling food_search and agriculture/climate 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?

Implies usage context through 'per Barcode' but lacks explicit when/when-not guidance regarding food_search alternative.

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