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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered structurally. The description adds real behavioral detail on top: the run window is capped at 100 recent runs, and the response bundles schedules, pending setups, deliveries, contacts and credits, plus the role gate. It stops short of explaining ordering or what happens beyond the 100-run cap.

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 that front-loads the resource, then the content of the result, then the permission gate. Every clause carries information; there is no filler or repetition of the title.

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?

With no input schema, no output schema and a read-only closed-world annotation set, the description is nearly complete: it names the returned sections and the 100-run ceiling. The only gap is that it doesn't say how to fetch older runs or whether the list is ordered, which an agent may want for follow-up calls.

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 to disambiguate and the schema is trivially complete at 100% coverage. The description appropriately spends no words on inputs and instead describes what comes back.

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 and resource ('Lists recurring lead request schedules') and enumerates the payload contents (pending setups, recent runs, companies delivered, contacts added, credits). An agent can tell this is a read of recurring-request configuration plus run history, distinct from listRequests or getRequest, though no sibling is named to make the contrast explicit.

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?

The description supplies an access constraint ('Workspace owners, admins and managers only'), which is genuinely useful routing context, but it never says when to choose this over listRequests or getRecurringRequestOptions, nor when a recurring-request listing is the wrong tool. Usage is implied rather than directed.

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