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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds only that these keywords feed link-prospect search; it says nothing about ordering, pagination, or what an empty result means for outreach setup.

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 no filler, which is appropriate for a simple list operation. It is efficient but too short to carry the missing selection and parameter context.

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 two-required-parameter tool with an empty schema description and no output schema, an agent is left without guidance on parameter sourcing or return shape. The annotation set is the only structured support, so the description should be doing considerably more.

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 there are two required parameters (projectId, siteId), yet the description mentions neither. With no way to know whether projectId and siteId are hierarchical, optional in practice, or what a site ID resolves to, 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 verb and resource ('List the keywords used to search for link prospects') and scopes it to outreach prospecting, which distinguishes it reasonably from list_article_keywords and list_lead_keywords. However, it never names those siblings explicitly, so the agent must infer the split from context.

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?

There is no guidance on when to use this versus the several other keyword-listing tools (list_article_keywords, list_lead_keywords, get_tracked_keywords, get_prospect_discovery). No prerequisites, no exclusions, no mention of the required project/site scoping as a selection condition.

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