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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered. The description adds two genuinely useful behavioral facts not in the annotations: overdue items are included, and results are sorted soonest-first. It says nothing about the look-ahead window or result size, which would be the remaining behavioral gap.

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 tight sentence with the resource, the filter, and the sort order front-loaded. Every clause carries information; nothing is wasted.

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 simple read-only list tool with annotations covering safety, the description is nearly adequate. However, with no output schema and no explanation of days_ahead or the returned lead fields, an agent cannot tell how to control the window or what it will receive.

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 0% and the sole parameter days_ahead (default 7, range 0-90) is never mentioned in the description. 'Follow-up due' vaguely implies a time window, but the agent gets no hint that the horizon is tunable or what the default is, so the description fails to compensate for the coverage gap.

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 resource (your leads) with a precise filter (follow-up due, including overdue) and an ordering guarantee (soonest first). This distinguishes it from broad siblings like find_leads or top_leads_to_call, though it doesn't name 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?

No when-to-use or when-not-to-use guidance and no mention of alternatives such as top_leads_to_call or find_leads. The agent must infer the selection condition from the phrase 'follow-up due' alone.

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