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

Annotations already declare this is a non-read-only, non-destructive, non-open-world write, so safety is covered. The description adds nothing beyond that: it does not say whether duplicate URLs are rejected, what happens on conflict, what permissions are needed, or what is returned. For a creation tool it leaves the behavioral profile largely unexplained.

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 front-loaded sentence with the verb first and no filler. It is efficient, though arguably too terse for a tool with four required parameters and zero schema documentation.

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 0% schema coverage, no output schema, and only sparse annotations, the description is the sole source of detail — and it provides almost none. An agent would know what the tool does in general but not how to populate projectId/siteId or what behavior to expect on success or failure.

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%, so the description must carry the parameter burden. It only loosely gestures at 'url' and 'title' ('a page of the website', 'articles should link to') and never mentions projectId or siteId at all, leaving two of four required identifiers completely undocumented.

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 uses a clear verb ('Add') and describes the resource conceptually ('a page of the website that articles should link to'), which is distinguishable from the sibling remove_internal_link_target and list_internal_link_targets. However, it never uses the term 'internal link target' itself and does not explicitly contrast with those siblings, so the differentiation is implicit rather than stated.

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 when-to-use guidance, no prerequisites (e.g., that a projectId/siteId must already exist), and no mention of alternatives such as list_internal_link_targets for inspecting existing targets or remove_internal_link_target for deletion. Usage must be inferred entirely from the tool name.

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