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

Annotations already declare readOnlyHint, openWorldHint=false, idempotentHint, and destructiveHint=false. The description adds meaningful behavioral context beyond those: deterministic execution, duplicate/retest lineage checks, optional owner-supplied limits, and exact exceptions with source-file/source-row provenance. No contradiction exists.

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 dense sentences front-load the core reconcile action and follow with secondary checks and return characteristics. Every sentence adds value with 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 4-parameter tool with strong annotations and an output schema, the description covers invocation behavior, selected checks, and provenance. The main gap is the lack of explicit guidance for distinguishing this tool from inspect_certification_package, which could complicate tool selection.

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 0%, so the description must carry parameter meaning. It maps csv_text to 'contractor certification CSV evidence', expected_ids to 'expected Cable IDs', and expected_test_limit to 'owner-supplied expected test limit'. It does not mention source_file, but the parameter name and default make it reasonably self-explanatory.

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 names a specific verb ('deterministically reconcile'), a resource ('expected Cable IDs against contractor certification CSV evidence'), and adds secondary checks (duplicate/retest lineage, expected test limit). The core purpose is clear, but it does not explicitly differentiate the tool from the sibling inspect_certification_package.

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 implies an audit/reconciliation scenario but provides no explicit guidance on when to choose this tool over cablecert_service_info or inspect_certification_package. No alternatives, exclusions, or preconditions are stated.

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