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

With no annotations provided, the description carries the full burden of behavioral disclosure and does so well: 'Return' indicates a read-only retrieval, 'fixed, published' signals deterministic, non-changing data, and 'Takes no arguments' confirms there are no inputs required. It could have added detail about output formatting, but for a zero-argument tool the disclosed behavior is largely sufficient.

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?

The description is a single well-structured sentence that front-loads the core purpose and then details the specific information returned. Every element earns its place; there is no filler or 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?

For a zero-argument tool with no output schema, the description fully covers what an agent needs to know: what the tool returns, the specific components included, and that no arguments are required. The tool's simplicity means nothing important is missing.

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?

The tool has zero parameters and the schema already documents this completely. The description reinforces this with 'Takes no arguments,' which is helpful and unambiguous. No additional parameter meaning is needed since there are no parameters to explain.

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?

The description uses a specific verb 'Return' and precisely names the resource: the fixed, published scoring methodology used by the Solar Quote Audit. It enumerates the exact contents included (four scoring dimensions, point weights, individual rules, rating thresholds), making the tool's purpose unmistakable. This clearly differentiates it from siblings like analyze_solar_quote, which would analyze a quote, and get_supported_regions, which returns regional data.

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?

The description makes clear this is the tool for retrieving the official scoring methodology, providing strong contextual guidance. It does not explicitly name alternatives or state when not to use it, but the stated scope ('fixed, published scoring methodology') makes its usage context easy to infer.

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