Backlinks Authority

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

No annotations exist, so the description carries full responsibility for behavioral disclosure. It only states 'Fetch authority metrics' without specifying which metrics are returned (e.g., domain authority score, page authority score, etc.), nor does it explain authentication, rate limits, or response structure. The absence of an output schema worsens the gap.

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, front-loaded sentence with no filler. However, it could be more informative without sacrificing conciseness, e.g., by noting what authority metrics include. Still, it avoids redundancy and earns its place.

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 the lack of output schema and the large set of sibling tools, the description fails to fully equip the agent. It does not explain return values, contrast with similar tools (getDomainAuthority, getPageAuthority), or provide usage examples, leaving the agent underinformed for correct invocation.

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%, so the description adds no new meaning beyond the schema descriptions. The parameter descriptions in the schema are adequate ('Target to assess authority...', 'Response format. Default: json.'). At baseline 3, no extra value is provided by the tool description.

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 verb 'Fetch', the resource 'authority metrics', and the scope 'target (domain, host or URL)'. It distinguishes from sibling tools like getDomainAuthority or getPageAuthority by emphasizing its applicability to any target format, including root domain, subdomain, or full URL.

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 is provided on when to use this tool versus related siblings such as getDomainAuthority or getPageAuthority. The description does not mention any prerequisites, exclusions, or alternative tools, leaving the agent to infer usage context without explicit direction.

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