Check a Deviation Against an ISO 2768-1 Note

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

No annotations are provided, so the description carries the behavioral burden. It usefully discloses that this is only a numeric comparison, requires a prior check that the dimension is unmarked, and does not establish process capability. It does not explicitly state that the operation is read-only or stateless, but for a pure calculation tool the main behavioral caveats are covered.

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 sentences, front-loaded with the core comparison and followed by the key precondition and limitation. Every sentence adds relevant guidance without repetition.

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?

With full schema coverage and an output schema, the description supplies the critical operational context an agent needs: this is numeric-only, applies only to unmarked dimensions, and does not imply process capability. Nothing essential is missing for correct invocation.

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%, so the parameters are already well documented. The description reinforces that the comparison concerns a stated deviation for one dimension and only applies to unmarked dimensions, but it adds no parameter-specific meaning beyond what the schema provides.

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 a specific verb and resource: compare a stated deviation numerically against the ISO 2768-1 general-tolerance value for one dimension. It also scopes the tool as a numeric comparison only and explicitly says the result does not establish process capability, which distinguishes it from capability or feasibility tools.

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 gives a clear prerequisite: first establish that the dimension has no individual tolerance indication, because general tolerance applies only to unmarked dimensions. It also excludes a misuse case by stating the result does not establish process capability, though it does not explicitly name an alternative sibling tool to use instead.

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