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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description usefully adds that nothing is opened or changed server-side, but the bulk of its behavioural content is about Vtiger's official API rate limits and lack of an MCP server, which explains the product's design rather than this tool's behaviour.

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 badly front-loaded: the operative fact that the tool only returns instructions is buried in the second sentence, after a clause that reads like a write action. The trailing sentence about REST API quotas, per-plan request counts and the 'checked 22 Oct 2026' audit note is tangential justification that does not help an agent decide or invoke.

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?

For a zero-parameter, no-output-schema tool with full annotation coverage, the essentials are there: what is returned (screens, buttons, fields) and what to do next. What is missing is any sense of the guide's shape or length and which specific browser tool to start with, leaving the agent to infer the handoff sequence.

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 tool takes zero parameters and the schema is fully closed (additionalProperties false), so there is no parameter meaning for the description to add. Baseline 4 applies; nothing about invocation is left ambiguous.

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 does reveal the real behaviour (it returns a step-by-step guide and 'opens nothing by itself'), but the opening clause 'Create case in the user's own Vtiger account' and the tool name both imply the creation actually happens, so the agent must read past the first sentence to learn the truth. It also never distinguishes itself from sibling vtiger_create_contact or vtiger_update_case, only from the cotlet_browser_* family.

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?

Some workflow guidance is present: 'then do it with the cotlet_browser_* tools in the user's Vtiger Cloud Browser' tells the agent what to call next. However, there is no explicit when-to-use versus alternatives such as cotlet_app_guide (which sounds like it serves a similar instructional purpose) or the other vtiger_* mutation tools, and no statement of prerequisites.

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