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

Annotations already declare readOnlyHint=true, destructiveHint=false and idempotentHint=true, and the description reinforces rather than repeats these by stating the tool 'opens nothing by itself' and only returns step-by-step screens/buttons/fields. It also explains why the guidance path exists — Vtiger's API allowance is 0 requests on One Pilot and 24,000/day (30/min) on One Growth, with no official MCP server — which is behavioral context not available in any structured field. No inconsistency with the annotations.

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 critical constraint ('opens nothing by itself') is front-loaded in the first sentence, followed by the next action and then the rationale. The API-limits sentence is long and slightly tangential, but it earns its place by justifying why a guidance-only tool exists instead of a direct integration.

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, read-only guidance tool with no output schema, the description covers what is returned (step-by-step screens, buttons, fields), what is not done (no side effects), and the correct follow-up tool family. Minor gaps remain around account prerequisites and whether the steps are tailored or generic, none of which would block correct invocation.

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 described (additionalProperties: false, empty properties), so there is nothing for the description to disambiguate. Baseline for a 0-parameter tool is 4, and nothing here lowers it.

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 definition names a concrete verb+resource and then immediately corrects the natural misreading of the name: the tool 'Returns how to do it in Vtiger step by step' and 'opens nothing by itself'. That said, the opening clause 'Convert contact to deal' restates the name and could momentarily imply the conversion is performed, so the distinguishing detail lands one clause later than ideal.

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 states the follow-on path explicitly: do the conversion 'with the cotlet_browser_* tools in the user's Vtiger Cloud Browser', which correctly routes the agent away from treating this tool as the executor. It provides no explicit when-not guidance (e.g., what to do if the account has API access or if the contact doesn't exist), but the surrounding context is clear enough to act on.

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