Noleemits Vision Builder MCP

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. It mentions checking activation status and retrieving stats, implying a read-only operation, but does not specify permissions, rate limits, or potential side effects. For a tool with zero annotation coverage, this leaves significant gaps in understanding its behavior and 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, efficient sentence: 'Check if Rank Math SEO is active and get overall SEO stats (posts with scores, posts with focus keywords).' It is front-loaded with the core purpose and uses parentheses to clarify the stats, avoiding any wasted words. Every part of the sentence earns its place by adding value.

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 complexity (simple read operation with no parameters) and lack of annotations or output schema, the description is minimally adequate. It explains what the tool does but does not cover return values, error handling, or integration context. For a tool with no structured output, more detail on expected results would improve completeness, but it meets the basic threshold.

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 input schema has no parameters (0 params, 100% coverage), so the description does not need to add parameter semantics. It appropriately focuses on the tool's purpose without redundant parameter details. The baseline for zero parameters is 4, as the description compensates by explaining what the tool does without unnecessary complexity.

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's purpose: 'Check if Rank Math SEO is active and get overall SEO stats (posts with scores, posts with focus keywords).' It specifies the verb ('check' and 'get') and resource ('Rank Math SEO' and 'overall SEO stats'), making the action explicit. However, it does not differentiate from sibling tools like 'get_seo_data', which might offer similar or overlapping functionality, preventing a score of 5.

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, such as 'get_seo_data' or other SEO-related tools in the sibling list. It lacks explicit context, prerequisites, or exclusions, leaving the agent to infer usage based on the purpose alone. This minimal guidance is insufficient for optimal tool selection.

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