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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It says what the table contains but does not explicitly say this is a read-only lookup, what the output format looks like, or how the optional 'option' parameter changes the result. The schema partially covers parameter behavior, but the description itself adds no behavioral context beyond content.

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, tightly worded sentence with no filler. The key phrase 'the full table' is placed at the end after an em dash for emphasis. Every word contributes to defining the tool's scope, earning a 5.

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 simple one-parameter, no-output-schema, no-annotation tool, the description plus schema parameter documentation provide the essential calling information. It names the domain and the full scope, and sibling tool names offer enough context for differentiation. The only gap is not describing return formatting, which is minor for a table lookup.

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 single parameter 'option' is already fully documented in the schema with 'one option's name, else all,' so schema coverage is 100%. The description's phrase 'each option's value' loosely maps to the parameter but adds no new meaning beyond what the schema already provides. Baseline 3 is appropriate because the schema handles the semantic weight.

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 identifies the resource (US HVAC field service software comparison) and the scope (every option's value on every criterion), calling it 'the full table.' It distinguishes from sibling tools like compare_criteria and compare_options by emphasizing the complete dataset rather than a focused subset. However, it lacks an explicit verb like 'returns' or 'displays,' which keeps it just short of a 5.

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 phrase 'the full table' implies this tool is for a comprehensive view, and sibling names like compare_criteria and compare_options suggest narrower alternatives. But the description never explicitly states when to choose this tool over those siblings or when not to use it. Usage guidance is only implied, not stated.

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