Solematica

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

Discloses data freshness ('aggiornato') and auth requirements ('Non richiede API key') in absence of annotations, though omits rate limits or caching details.

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?

Two dense sentences covering scope, data fields, and auth; no redundancy or filler content.

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?

Adequately compensates for missing output schema by enumerating return data points (prezzi, brand, garanzie), sufficient for simple parameterless tool.

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?

Zero-parameter tool meets baseline expectation; description appropriately silent on parameters since schema is empty.

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 (restituisce/confronto) and resource (offerte fotovoltaico) with explicit differentiation from sibling 'dettaglio_provider' via multi-operator comparison scope.

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?

Usage is implied by the comparison framing vs sibling tools, but lacks explicit when/when-not guidance or alternative selection criteria.

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