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

No annotations exist, so the description carries the full burden. It usefully discloses the return shape ('normalized JSON') and a notable behavior ('line-by-line math verification'), but omits read-only vs. mutation semantics, size/length limits on document_text, and failure modes for unparseable documents.

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?

A single front-loaded sentence that is information-dense and wastes little. The 'API #10:' prefix is a non-functional label that consumes tokens without helping selection or invocation.

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 3-param extraction tool with no annotations and no output schema, the description covers the input types, the normalization/verification behavior, and the return format. Missing details on the two undocumented parameters and handling of malformed input keep it short of full completeness.

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 only 33% (only document_text is documented), so the description must compensate. It partially does by implicitly mapping to the expected_document_type enum values (CLIN/SLIN schedule, GSA/T&M rate card, BOM), but never explains expected_document_type or audit_math_and_anomalies directly.

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?

States a specific verb (extract) and resource (multi-tier CLIN/SLIN pricing tables, labor rate cards, BOM spreadsheets) and names the concrete outputs, so an agent can distinguish it from siblings like parse_b2b_contract or generate_compliance_matrix without opening a schema.

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 input domain is clear ('from unstructured vendor quotes or Section B schedules'), which implies when to use it. However it offers no explicit exclusions or named alternatives, and the pricing-extraction overlap with sibling parse_b2b_contract is left unaddressed.

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