far_compliance_matrix

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

The description goes well beyond the readOnlyHint and openWorldHint annotations. It details how unresolved clauses are handled (404 vs errored buckets), deduping case-insensitively, gate flagging behavior, and the asOfDate parameter for point-in-time codification. It also notes 'Keyless' for authentication. This provides comprehensive behavioral disclosure.

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 relatively long but every sentence provides necessary detail. It is front-loaded with the main purpose. Some minor redundancy (e.g., 'TRUTHFUL by construction' could be integrated), but overall it is well-structured and efficient for the complexity.

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 (composing far_clause_lookup, error handling, gate flags, point-in-time) and the absence of an output schema, the description is remarkably complete. It explains each output field (clause text, prescription, regulation, gate flag) and the summary.total field. It covers edge cases like unresolved vs errored clauses and the purpose of each parameter.

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?

All four parameters have descriptions in the input schema (100% coverage), so the baseline is 3. The description adds extra context beyond the schema: it explains that clauses come from e.g., 52.252-2 lists, deduping is case-insensitive, defaults for boolean parameters (flagGates and includePrescription default true), and the asOfDate defaults to current up_to_date_as_of. This adds significant value.

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 clearly states the tool's action: 'Turn a solicitation's cited FAR/DFARS clause list into a proposal-ready compliance matrix.' It specifies the input (clause list) and output (matrix for Section L/M response). It distinguishes from siblings by noting it composes far_clause_lookup over multiple clauses, which is a distinct function from individual lookup 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 explicitly states when to use the tool (have a list of clause numbers from a solicitation) and what it does not do: 'Does NOT parse the PDF solicitation to extract the clause list, and gives NO legal advice or compliance verdict.' It also notes 'for a Section L/M response,' providing context. While it doesn't directly compare to siblings, the purpose is self-contained.

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