Seo Api2 MCP Server

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. 'Broken Links Finder' gives no indication of what the tool actually does operationally—whether it scans a single page or entire site, returns structured data or raw text, has rate limits, requires authentication, or what constitutes a 'broken' link. This leaves critical behavioral traits completely unspecified.

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?

While extremely concise (two words), this is a case of under-specification rather than effective brevity. The description fails to convey essential information, making it inefficient for its purpose. Every word should earn its place, but here the words provide almost no value beyond the tool name itself.

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 tool's apparent complexity (finding broken links typically involves web crawling and HTTP status checks), no annotations, no output schema, and a completely inadequate description, this is severely incomplete. The description fails to explain what the tool returns, how it operates, or any behavioral context, leaving the agent with insufficient information to use it effectively.

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%, with both parameters ('url' and 'page') documented in the schema. The description adds no additional meaning about parameters beyond what the schema provides, such as clarifying the 'url' parameter's purpose or how 'page' affects pagination. With high schema coverage, the baseline score of 3 is appropriate as the description doesn't compensate but doesn't need to.

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 'Broken Links Finder' is a tautology that merely restates the tool name without adding any meaningful information about what the tool actually does. It doesn't specify what action is performed (e.g., 'find', 'scan', 'detect') or what resource is involved (e.g., 'on a webpage', 'in a website'). No distinction from sibling tools is provided.

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. There is no mention of context, prerequisites, or comparison with sibling tools like 'link_analyzer' or 'redirect_checker' that might have overlapping functionality. Users must guess when this specific tool is appropriate.

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