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

No annotations are provided, so the description must carry the full burden of behavioral disclosure. It mentions the action and output format but does not disclose any side effects, authorization requirements, data volume, or return behavior (e.g., whether the CSV is always available, if it may be truncated, or if it requires specific permissions). This is a significant gap for a tool with zero annotation coverage.

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 a single, well-structured sentence that front-loads the action and resource, then lists the specific fields. It contains no redundant or vague phrasing, and every word earns its place.

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 simplicity (no parameters, no output schema), the description covers the output format and fields, but it omits practical caveats such as data size limits, authentication requirements, or whether the export is always available. With zero annotations and no output schema, a bit more detail about the return type or potential risk (e.g., large data) would improve 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?

The tool has no parameters, so there is nothing for the description to add beyond the schema. The baseline of 4 is appropriate because the description correctly omits parameter details that are irrelevant.

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 ('Export') and a defined resource ('the full subcontractor compliance report') along with the output format (CSV text) and the included fields. This makes the tool's purpose unmistakable and distinguishes it from sibling tools that retrieve summaries or specific subsets.

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 that this tool should be used when a complete, exportable report is needed, but it does not explicitly mention when to use this tool versus the siblings (e.g., get_compliance_summary for a summary, list_uninsured_subs for uninsured subs). No exclusion criteria or alternatives are given, leaving usage to inference.

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