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

Beyond the readOnlyHint/idempotentHint annotations, the description discloses the crucial behavioral fact that the tool 'opens nothing by itself' and only returns instructions, so no mutation occurs. It also surfaces external constraints (Vtiger REST API quotas of 0 for One Pilot and 24,000/day for One Growth, no official MCP server) that shape how the agent should proceed.

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 key point — that this returns instructions rather than performing the action — is front-loaded in the first two sentences. The API-limits sentence is somewhat dense and tangential but earns its place by explaining why the browser-tool path exists.

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?

With no parameters, no output schema, and read-only annotations, the description covers what an agent needs: what it returns, that it performs no action, and which tools to use next. The only mild gap is the exact shape/format of the returned guide, which is described only in general terms.

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, so there is nothing for the description to disambiguate and the baseline applies. The description doesn't need to compensate for any schema gap.

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 states concretely that the tool returns a step-by-step guide (screens, buttons, fields) for creating a contact in the user's own Vtiger account, which is more specific than the title and resolves the ambiguity of the 'create' name. It distinguishes itself from the cotlet_browser_* siblings by handing off the actual execution to them, though it doesn't contrast with vtiger_list_contacts or other vtiger_* siblings.

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?

It gives a clear workflow: call this to get the procedure, then carry it out with cotlet_browser_* tools in the Vtiger Cloud Browser. The API-limits note explains why the direct-API path isn't used, which implicitly justifies choosing this tool, but there is no explicit 'do not use this if...' exclusion.

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