Get Found Links

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

No annotations provided, so the description must convey behavioral traits. It only states it returns a paginated list but does not disclose pagination behavior, data freshness, rate limits, or that this is a read-only operation. The description lacks sufficient detail for an agent to understand side effects or constraints.

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 front-loaded. It contains no fluff and succinctly conveys the core purpose.

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 5 parameters (including a nested filter array) and no output schema, the description should cover return structure, pagination details, and filter usage. It only mentions 'paginated list' without explaining offset/limit. The description is incomplete for an agent to effectively invoke the tool without additional schema parsing.

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 100%, so the schema already documents all parameters. The description does not add extra meaning beyond what's in the schema. For instance, the filter array is complex but the description doesn't explain how to build filters. The description remains at baseline because it doesn't compensate for schema descriptions.

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 is clear: 'Returns a paginated list of every hyperlink discovered across the entire site during the audit.' It uses a specific verb ('Returns') and resource ('paginated list of hyperlinks') and distinguishes from sibling tools by focusing on hyperlinks found during an audit, not other link types.

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 guidance on when to use this tool versus alternatives (e.g., other getBacklinks tools). The description only states what it does, not when to use it or when to avoid it. For example, it doesn't clarify if this is for internal links only or all links, nor does it mention prerequisites.

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