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

Annotations already declare readOnlyHint=true, destructiveHint=false, openWorldHint=false, so safety is covered, but the description adds nothing beyond them: no indication of result volume, pagination, whether results are scoped per site, or how 'targets' are determined. For a list tool that may return many rows, that is a meaningful gap.

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?

One short sentence with no filler, so it is not bloated — but the brevity here reads as under-specification rather than precision. Nothing is front-loaded because there is nothing to front-load.

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?

A two-required-parameter list tool with no output schema relies on the description for scope, return shape, and ordering, and the description supplies none of it. It only says what the items conceptually are, not what an agent gets back or how to interpret it.

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 required parameters (projectId, siteId) have 0% schema description coverage, and the description never mentions them, so nothing explains the scope these IDs impose or what happens if they disagree. The parameter names are fairly self-describing, which keeps this from a 1, but the description contributes no semantics.

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?

It states a verb (list) and a roughly identifiable resource (pages articles may link to), so the agent can guess it returns a set of internal linking candidates. But the phrasing is imprecise — 'allowed to link to' does not clarify whether these are CMS pages, article targets, or linkable assets, and no sibling (e.g. list_linkable_assets, list_articles, list_sites) is distinguished.

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 statement of when to use this tool, when not to, or which sibling to choose for related needs. With many list_* siblings covering overlapping content surfaces, the agent gets no routing guidance at all.

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