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

Annotations already declare readOnlyHint=true, idempotentHint=true and destructiveHint=false, so the safety profile is covered for the agent. The description reinforces that this is a pure read by saying it "Returns" allowance facts, but adds nothing about units, freshness, or scope (per request vs. per account) beyond that.

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, zero filler: the first states the return content, the second states the purpose. The most useful information (what it returns) is front-loaded.

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?

There is no output schema, so the description carries the burden of describing return values, and it does so at a high level (contacts per company count and phone-enrichment flag). A minor gap remains: the exact shape/units of the response are not spelled out, but for a parameterless informational lookup this is largely sufficient.

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 tool takes zero parameters, so there is nothing for the description to disambiguate and the baseline is 4. The description correctly avoids inventing inputs and frames the call as a parameterless lookup.

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 names a specific verb and returned resource: it states the tool returns the contacts-per-company allowance in a lead request plus whether phone enrichment is included. That is concrete enough to distinguish it from credit/quota siblings like getCreditBalance or getCredits, though it never names those siblings explicitly.

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?

"Use it to price a lead request" gives one clear trigger for calling the tool. There is no guidance on when not to use it and no routing to alternatives such as getCreditBalance or getRecurringRequestOptions, which an agent may confuse with allowance/pricing information.

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