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

With no annotations, the description carries the full burden. It discloses that output is sim-derived with no interpretation drift, includes a strong anti-fabrication statement that deltas are computed and not estimated, and instructs to quote verbatim. This gives the agent critical behavioral guardrails.

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 information-dense with no filler. Each sentence serves a distinct purpose (definition, output nature, usage, anti-fabrication) and it is front-loaded with the core purpose. The length is justified by the critical 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?

Given the tool's complexity (comparison of multiple metrics) and lack of output schema, the description provides everything needed: what it compares, that output is sim-derived, when to use it, and how to handle numbers. The schema covers parameter selection. No significant gaps remain.

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 100% with both parameters having descriptions and enums. The tool description adds context about what the comparison includes but does not further explain the parameter meanings. The schema already does the heavy lifting, so baseline 3 is appropriate.

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 states the specific verb 'comparison' and the resource 'two chapters', listing the compared aspects (tracks, topology, OEE, throughput, headline bottleneck). This clearly distinguishes it from siblings like get_chapter_facts (single chapter) or explain_concept (concept discussion).

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 provides three explicit usage scenarios ('how does X compare to Y?', 'what's the difference between Constraint-Level and LEDS-Level?', 'what changes when we add buffers?'), which gives clear context. However, it does not include explicit when-not-to-use or alternative tool names, so it falls short of a 5.

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