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

Annotations already declare readOnlyHint and openWorldHint, so the safety profile is covered. The description adds two material traits the annotations don't: determinism (reproducible output for identical inputs) and a concrete cost/payment rail ($0.25 USDC on Base via x402), which is critical for an agent deciding whether to call it. It still omits what happens on payment failure or how long scoring takes.

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?

Two tight sentences with no filler, and the core purpose is front-loaded ahead of the cost note. It is efficient, though the extreme brevity contributes to the gaps in other dimensions.

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?

With four parameters, 0% schema descriptions, and no output schema, the description should compensate for input semantics and expected result. It supplies only the payment model, leaving the agent unable to construct a valid, meaningful call from the description alone.

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%, so the description carries the full burden and largely fails it. 'seven-pillar' loosely hints at the pillars array (maxItems 7), but opportunityName, stage, and redFlagIndices are entirely unexplained, including what the red-flag indices refer to and how many pillars are expected.

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?

It names a specific resource and result ('opportunity score') and a distinguishing trait ('seven-pillar', 'deterministic'), but 'score' is used as a noun without a clear verb, and neither 'opportunity' nor 'pillar' is defined. An agent can't tell from this alone what domain the opportunity belongs to or what the score represents. It does separate itself from the base_* and audit_* siblings, which matters.

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 only guidance is a price tag; there is no statement of when to use this tool versus siblings, what input is required, or what preconditions exist beyond paying. The payment note is a precondition, not usage routing, so the agent is left to infer everything about selection.

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