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

Annotations already declare non-destructive, idempotent, open-world behavior, so the safety profile is covered. The description adds useful cost context ($0.08 USDC per call) and outlines the output, but says nothing about the internal behavior of scoring or the required lead shape.

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 sentences, tightly front-loaded with the core action and the pricing/context tag at the end. No wasted words, though the signals list is slightly dense.

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 output side (a 0-100 score with signals and next action) is described despite no output schema. However, with a nested required object and 0% schema coverage, the description should define what the lead/context inputs look like, which it does not.

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% and the description only implies a 'lead' input. The 'context' parameter is never mentioned, and the required 'lead' object (additionalProperties: {}) is left totally undefined, so an agent cannot infer what to pass.

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 resource (inbound leads), plus the output range (0-100) and the signals produced. Clear enough to distinguish, though it does not name or contrast any sibling.

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?

'Built for insurance/ad-sales funnels' implies the intended domain, but there is no explicit when-to-use, when-not-to-use, or alternative routing. Usage is only inferred from the domain hint.

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