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

With no annotations, the description carries the full disclosure burden. It does disclose meaningful non-behaviors: it does not submit bids, contact the Government, make certifications, or create payment, and it restricts inputs to public/buyer-authorized non-sensitive information. However, it does not describe side effects, data persistence, authorization mechanics, or what the tool actually does beyond 'run' a preview.

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 two sentences with no filler. The first sentence front-loads the action and data constraint; the second efficiently clarifies the tool's non-actions. Every sentence serves a purpose, and the length is appropriate for the content conveyed.

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?

The tool has 4 parameters, two deeply nested objects, zero schema descriptions, no output schema, and no annotations – a complex invocation surface. The description does not explain how to construct the nested objects, what the expected result format is, or what the qualifier preview actually evaluates. An agent cannot reliably call this tool correctly based solely on this text.

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%, and the description adds no parameter-level meaning. It does not explain 'opportunity', 'company_profile', 'pursuit_role', or 'buyer_reference' – their purpose, structure, or constraints. The only input hint is 'non-sensitive information', which is too generic to guide construction of the nested objects.

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 uses a specific verb ('Run') and names the exact resource ('Cropper Industries Federal Opportunity Qualifier shadow preview'), making the tool's identity clear. It also distinguishes it from siblings by emphasizing that it is a preview and listing actions it does not take. However, it never explicitly states that the tool assesses or qualifies an opportunity against a company profile, leaning on the tool name for that core meaning.

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?

There is no guidance on when to use this tool versus its siblings ('govomniai_transaction_assurance_shadow', 'list_machine_services') or when not to use it. The phrase 'free ... shadow preview' hints at a non-production use case, but no decision rule or alternative selection criterion is provided.

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