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. It states the tool performs a deletion, which implies a destructive mutation, but it doesn't disclose behavioral traits such as permissions required, whether the deletion is reversible, error handling, or any rate limits. This is a significant gap for a mutation tool with zero annotation coverage.

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 that front-loads the core action and includes the alias information without unnecessary details. Every word earns its place, making it highly concise and well-structured for quick understanding.

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 is a destructive mutation with no annotations and no output schema, the description is incomplete. It lacks critical context such as what happens post-deletion, error scenarios, or return values, which are essential for safe and effective use. The high schema coverage doesn't compensate for these behavioral gaps.

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 100% description coverage, with clear parameter names and descriptions, so the baseline is 3. The tool description does not add any meaning beyond what the schema provides (e.g., it doesn't explain parameter formats or interactions), so it meets but does not exceed the minimum viable level.

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 action ('Delete') and resource ('Elementor element from a page'), making the purpose specific and understandable. It also mentions it's an alias for 'delete_element', which helps distinguish it from other deletion tools like 'delete_page'. However, it doesn't fully differentiate from 'delete_element' beyond the alias note, keeping it from a perfect score.

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 implies usage by specifying it deletes an element from a page, but it lacks explicit guidance on when to use this tool versus alternatives like 'delete_element' (beyond noting it's an alias) or other deletion tools. No context on prerequisites or exclusions is provided, leaving usage somewhat ambiguous.

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