get_report_quote

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

Annotations declare readOnlyHint: true. Description adds that it counts cached properties and estimates fresh-fetchable records, disclosing non-destructive behavior and billing info. No contradiction.

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 concise sentences front-loaded with purpose. No wasted words; every sentence adds value.

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?

No output schema, but description outlines output shape (counts cached and estimate of fresh records). Parameter details are sparse; however, for a preview tool with read-only safety, it's minimally adequate but could elaborate on output format.

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 only 11%, and description does not elaborate on individual parameters (e.g., value_min, roof_material). Only storm_id has a description in schema. The description mentions 'filters' generically but adds no specific param meaning.

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?

Description specifies it's a cost preview for get_swath_report, clearly distinct from sibling tools like get_swath_report (returns rows) and find_storms (finds storms). Uses specific verb 'preview' and resource 'cost'.

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?

States 'Use before pulling large reports,' providing clear context. Lacks explicit when-not-to-use or alternatives, but the usage instruction is straightforward and helpful.

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