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

Annotations already declare readOnlyHint=true, openWorldHint=false, and destructiveHint=false, so the safety profile is covered. The description adds essentially no behavioral context beyond the purpose statement — nothing about pagination, filtering, empty-result behavior, or whether the list is configuration-derived. With the annotation bar already met, this adds no incremental disclosure.

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 or redundancy. It is efficient, though its brevity borders on under-specification given everything else the tool leaves unsaid.

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 simple read-only list tool with no output schema, the description is minimally adequate: the agent knows it retrieves allowable internal link targets. However, with two required undocumented parameters and no mention of scoping or result shape, it is thinner than this tool's context warrants.

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 and schema description coverage is 0%, so neither is documented anywhere. The description does not explain what a site vs. a project is or how the two scope the returned targets, so it 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?

The description states a clear verb (List) and defines the resource in domain terms: pages that articles are permitted to link to. That is more informative than the bare name 'internal_link_targets'. It stops short of distinguishing itself from adjacent siblings such as list_linkable_assets or add_internal_link_target/remove_internal_link_target.

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?

No indication of when to call this versus alternatives, no prerequisites (e.g. must targets be configured first?), and no note that it is scoped per project/site. The agent must infer usage from the name and the two required parameters alone.

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