Solematica

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

Discloses critical requirements (API key with credits) and methodology (satellite analysis) that schema doesn't cover; no annotations provided to contradict.

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?

Three well-structured sentences: purpose, capabilities/methodology, and requirements—every sentence earns its place with no redundancy.

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?

Lists calculated outputs (production, savings, ROI, sizing) compensating for missing output schema; could briefly mention output format/structure.

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 description coverage is 100%, establishing baseline 3; description mentions 'indirizzo' contextually but doesn't need to elaborate given comprehensive 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?

Clear specific action (estimates PV potential) with resource (Italian address) and distinguishes from siblings like info_tetto or prezzi_energia by mentioning satellite analysis and financial calculations.

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 specific domain (solar estimation vs siblings for articles/providers/energy prices), but lacks explicit when/when-not guidance or comparison with info_tetto.

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