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

Annotations already declare readOnlyHint=true, openWorldHint=false, destructiveHint=false, so the safety profile is covered. The description adds the output shape (templates and headings for topic matching), but discloses no pagination, rate, or scoping behavior 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?

Two compact sentences, front-loaded with what is returned and followed by the purpose. No padding, though the closing clause about headings partly restates the earlier field list.

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 correctly carries the return-shape burden by listing the fields, and the tool is a simple optional-param read. Only pagination or result-size behavior is absent, a minor gap for this read-only list tool.

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?

The single workspaceId parameter is fully documented in the schema (100% coverage), including its default behavior. The description adds nothing about it, which is acceptable given the schema does the work, so the 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 concrete verb and resource ('List posts as internal-link targets') and enumerates the returned fields (id, slug, title, description, headings, template), which distinguishes it from the plain list_posts sibling by the linking purpose. It never names list_posts explicitly, so the differentiation is implied rather than foregrounded.

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 phrase 'so the next article can take a different shape' conveys the intent (picking internal-link targets before writing), which implies usage. There is no explicit when-not guidance and no alternative tool named, so it stays at implied context rather than routing.

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