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 states 'Get the preview URL' which implies a read-only operation, but doesn't specify if this requires authentication, has rate limits, returns a temporary or permanent URL, or what happens on errors. For a tool with no annotation coverage, this leaves significant behavioral gaps.

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, clear sentence with zero wasted words. It's front-loaded with the core purpose ('Get the preview URL'), making it immediately understandable. Every word earns its place by specifying the action and target.

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 low complexity (1 parameter, no output schema, no annotations), the description is minimally complete. It states what the tool does but lacks behavioral details and usage context. Without annotations or output schema, the description should ideally cover more about the return value (e.g., URL format) and operational constraints, but it's adequate for basic understanding.

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 the single parameter 'page_id' documented as 'Page ID' in the schema. The description doesn't add any meaning beyond this—it doesn't explain what constitutes a valid page ID, where to find it, or provide examples. With high schema coverage, the baseline is 3, and the description doesn't compensate with additional context.

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 ('Get') and resource ('preview URL for a page'), making the purpose understandable. It distinguishes from siblings like 'get_page' (which likely retrieves page data) by focusing specifically on the preview URL. However, it doesn't explicitly mention what distinguishes it from tools like 'get_page_structure' or 'get_post_content', so it's not fully specific about sibling differentiation.

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. With siblings like 'get_page', 'get_pages', and 'get_page_structure', there's no indication of when a preview URL is needed instead of other page-related data. No context, exclusions, or prerequisites are mentioned.

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