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. The description adds useful content about what is aggregated (the four funnel stages) but says nothing about permissions, rate limits, or whether the numbers are scoped to the caller's workspace.

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: the metric list first, the usage trigger second, with no filler. Everything present earns its place, though the second sentence is fragmentary rather than fully structured.

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?

No output schema exists, so the description must convey what comes back — and it does by naming the four funnel metrics returned. The absence of any note on scoping or empty-result behavior keeps it from being fully complete.

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 100%, and both parameters carry their format ('YYYY-MM-DD (inclusive)') in the schema. The description only restates 'over a date range', adding no boundary, timezone, or default behavior beyond what the schema supplies. Baseline 3 applies.

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-resource computation ('Quote-to-close funnel over a date range') and enumerates the exact metrics computed: quotes created, sent/pending, accepted, and accepted rate. It is clearly distinct from quote-listing siblings like find_quotes or quotes_to_follow_up, though it does not name those alternatives.

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?

It gives explicit trigger phrases in quotes — 'conversion rate' / 'pipeline funnel' — which tells the agent when this tool is the right one. It stops short of stating when not to use it or what sibling to pick for raw quote retrieval.

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