document_backlinks

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

With no annotations, the description carries the burden of disclosure. It mentions a conditional requirement ('when the capability is installed') but does not explain behavior when the capability is missing, error scenarios, or any other side effects. Minimal transparency.

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?

The description is a single sentence that front-loads the action and resource with no fluff. It earns its place, though brevity comes at the cost of completeness.

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 one-parameter listing tool, the description provides the basic return expectation ('list incoming document links') but lacks detail on the 'capability' prerequisite, error handling, or how slug is used. No output schema exists, so the description is the only source of return information, making it somewhat incomplete.

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 schema has 0% description coverage and the tool description does not explain what 'slug' refers to. This is a single required parameter with no semantic guidance in either the schema or description, leaving the agent without enough information to correctly supply it.

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 clearly states the action (list) and the resource (incoming document links), distinguishing it from the sibling tool document_links which likely lists outgoing links. The phrase 'incoming' adds specificity.

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 description implies usage for listing backlinks but provides no explicit comparison to alternatives or exclusions. The caveat 'when the capability is installed' hints at an availability condition but does not clarify when to prefer this tool over document_links.

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