Backlinks Indexed Pages

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

No annotations are provided, so the description must disclose behavioral traits. It mentions sorting and limit controls (already in schema) but omits details like pagination behavior, whether results are exhaustive, rate limits, or permission requirements. The description adds minimal value beyond the input schema.

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 is direct and to the point. Every word adds value: it identifies the tool category ('Data Tool'), the action ('Fetch'), the resource, and key features (sorting and limit controls). No unnecessary text.

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?

Given there is no output schema, the description should clarify what the output contains. It does not describe the return format (e.g., list of URLs with counts) or error handling. The tool's role is clear, but for a data retrieval tool, the lack of output details leaves a gap.

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 coverage is 100% with detailed parameter descriptions, so baseline is 3. The description adds the phrase 'with sorting and limit controls' but does not provide extra meaning beyond what the schema already offers. No examples or typical usage are included.

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 tool fetches 'site pages that have backlinks' with sorting and limit controls, specifying the verb 'Fetch' and resource 'site pages with backlinks'. This distinctly differentiates it from siblings like DATA_getAllBacklinks (which returns backlinks, not pages) and other backlink tools.

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 provides no guidance on when to use this tool versus alternatives. It does not mention prerequisites, recommended scenarios, or when not to use it. The only context is the tool name and description, which requires the agent to infer usage from its function.

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