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

Annotations already declare readOnlyHint=true and destructiveHint=false, covering the safety profile. The description adds that the tool is 'negation-aware' and 'supplier-backed', giving some insight into its logic. However, it does not explain what negation-awareness means in practice, what data sources are used, or what the response looks like. No contradiction with the annotations.

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 efficient sentence with no filler and the core verb 'assess' front-loaded. It packs several concepts into nine words, though the dense jargon makes it slightly cryptic and reduces clarity.

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 tool with one parameter and no output schema, the description should at least clarify how this differs from assess_opportunity_eligibility, what kind of result is returned, and what 'negation-aware' means. None of that is present. While the read-only annotation covers safety, an agent cannot confidently decide when to call this tool or interpret the result.

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 schema has one required opportunity_id with no description (0% coverage), so the description must compensate. It does tie the parameter to 'a funded opportunity', which is meaningful context not present in the schema. Yet it leaves out format, source, or how the ID is resolved, so compensation is only partial.

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 composite assessment – eligibility plus supplier-backed price/cost – for a funded opportunity. It is clear enough to convey the core function and vaguely distinguishes itself from the sibling assess_opportunity_eligibility, but the terms 'negation-aware' and 'supplier-backed' are unexplained jargon that leave the exact meaning fuzzy.

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 explicit guidance on when to use this tool versus assess_opportunity_eligibility or other assessment sibling tools. The only inference is from the word 'real' and 'funded opportunity', which is not a stated rule or condition. The agent is left to guess.

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