get_leads

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint, and the description reinforces and expands on these by stating it creates, changes, and deletes nothing. It adds valuable context about server-side auth, throttling, retry behavior, and error response semantics beyond what annotations provide.

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?

The description is well-structured with clear labels: Behavior, Parameters, Returns, Use when. It is detailed yet efficient; every section adds operational value without unnecessary fluff.

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 paginated list tool with one optional parameter and no output schema, the description covers behavior, auth, rate limiting, pagination, response format, error handling, and appropriate use cases. Nothing important is missing for an agent to invoke it correctly.

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 coverage is 100%, and the schema already documents the page parameter including default and out-of-range behavior. The description adds only a mild reminder to 'walk them with page', which is useful but does not substantially extend the schema's meaning.

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 the verb and resource clearly: 'Get leads. Returns a list with all the leads of the school.' It also adds scoping detail (all school leads), sorting, and pagination. This distinguishes it from related tools like get_leads_per_affiliate.

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 provides an explicit 'Use when' section: safe to call speculatively for lookups and reporting, and says not to use it for changing anything. It references the matching write tool but does not name a specific sibling, so exclusions are present but alternatives remain somewhat generic.

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