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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered and "Score" is consistent with a read operation. The description adds real non-annotation behavior — the paid, credit-consuming, production-billing gate — which is valuable. It does not disclose what the score looks like (scale, interpretation) even though no output schema exists.

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 short sentences with zero filler; the core purpose is front-loaded and the billing constraint follows immediately. Every clause carries information.

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 scoring tool with no output schema, the description should at least characterize the returned score or how to interpret it, and it does not. The billing prerequisite and the four scored dimensions are covered adequately, but the output side is a clear gap.

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 coverage is 0%, so the description must carry the burden. It names all four parameters and frames them as "evidence ... supplied by a salesperson," which implies the booleans mean presence/absence of evidence — a meaningful addition over bare true/false fields. It still does not define what true or false means for each dimension or how partial evidence is handled.

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?

States a specific verb ("Score") and names the exact resources scored: need, budget, authority, urgency — the BANT framework — plus the input source (a salesperson). An agent can tell this is a lead-qualification scoring tool, though nothing in the text distinguishes it from the many sibling checker tools by name.

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 gives a precondition ("PAID ONLY: 5 prepaid credits; production billing required") and implies the input must come from a salesperson, which is genuine usage context. It does not say when to prefer this over alternatives or when the tool is inappropriate (e.g., non-B2B leads).

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