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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so safety is covered. The description adds only the loose semantic gloss ('pages the user pitches'), and says nothing about scoping by project/site, whether it can return empty, or what the returned pages look like.

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?

It is a single compact sentence with no filler, which is good, but the brevity is under-specification rather than efficiency – there is room for one clarifying clause about the scope or return set that would pay for itself.

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 output schema, the description should at least sketch what the list contains (page URL, title, pitch status?) and how the two required identifiers scope it. Neither is present, so an agent has to call the tool to learn what it returns.

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?

Both parameters (projectId, siteId) are required with 0% schema description coverage, so the schema provides no meaning at all. The description never mentions either parameter or explains how the two scopes combine (e.g., whether siteId narrows results within projectId), so the agent is left to guess.

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?

The description pairs a verb (list) with a resource (pages pitched in outreach), but never defines what a 'linkable asset' actually is, and the title/name ('linkable assets') and the body ('pages the user pitches') use two different vocabularies. With ~80 sibling tools including list_distribution_pages, list_internal_link_targets, and list_backlinks, an agent cannot easily tell which list this is without guessing.

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 list_backlinks, list_distribution_pages, or list_internal_link_targets, and no stated prerequisites or exclusions. The only contextual cue is the word 'outreach', which implies a domain but leaves the selection decision to inference.

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