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

Annotations already declare readOnlyHint=true, openWorldHint=false, and destructiveHint=false, so the agent knows this is a safe, closed-domain read. The description adds that the payload includes per-trade economics and call-type/unanswered-call characteristics, but says nothing about ordering, size, or stability of the list, which is the sort of context a reference lookup benefits from.

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?

A single sentence with no filler, front-loaded with the resource ('the home-service trades FindingLeads serves'). It is slightly dense in its trailing clause but every element carries information about the returned fields.

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 must communicate the return shape — and it does, listing three of the per-trade attributes an agent will receive. Combined with annotations that establish the read-only, closed-world nature, this is close to sufficient; only ordering or list-size behavior is left unstated, which is minor for a static enumeration.

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 no parameter semantics burden and the baseline of 4 applies. The description correctly implies the tool is unfiltered, returning all trades rather than accepting a query.

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 the resource ('the home-service trades FindingLeads serves') and enumerates the attributes returned (typical booked-job value, call type, unanswered-call frequency), so an agent can tell this is a reference lookup of trades. It never uses an explicit verb like 'list', relying on the name to carry that, and it does not differentiate itself from any sibling, but the resource is unmistakable.

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 when-to-use guidance, no stated prerequisites, and no mention of alternatives among the ten siblings. The only implied usage is that this is a static reference list an agent might consult before calling tools like estimate_missed_call_cost or get_pricing, but that is inference the description never supports.

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