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

Annotations already declare readOnly, idempotent, non-destructive, so the safety profile is covered. The description adds traits the annotations cannot: the domain-authority read is LIVE and never cached, scores are never fabricated, the call costs no credits, and the tool's scope is white-hat research/outreach only. That is meaningful context beyond structured fields.

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 front-loaded sentence with no filler; the ordering, enrichment, cost, and scope each earn their clause. Slightly dense with four colon-separated claims, but 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 one-parameter list tool with no output schema, the description tells the agent what comes back (prospects enriched with live DA) and in what order. Pagination is not addressed, though 'every prospect' implies a full return; otherwise nothing an agent needs to call it correctly is missing.

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%, so projectId is fully documented in the schema ('Required. The MisarSEO project ID... Get one from list_projects'). The description adds no parameter-level meaning, so 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?

States a specific verb and resource with scope and ordering: 'every prospect for a project, newest first'. An agent can tell it apart from the write siblings (add_link_prospect, update_link_prospect) and the export sibling by the resource and read framing. It stops short of naming any alternative, so it's clear but not fully differentiated in prose.

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 implies the usage context (browse a project's prospect pool) and volunteers 'FREE (no credits)', which is a real selection signal against metered alternatives. However it never states when to use this over list_link_prospect_activity or export_link_prospects_csv, so the guidance is implied rather than explicit.

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