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

Beyond the annotations, it discloses that the call performs no side effects, returns a step-by-step procedural answer, and that Setup requires an admin-created OAuth2 client since there is no official MCP server. That is meaningful behavioral context an agent could not infer from readOnlyHint/idempotentHint alone. It stops short of describing the return structure or length.

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?

Everything sits in three front-loaded sentences that each carry a distinct point: what it returns, that it does nothing itself, and what to do next. The appended API/OAuth note with a dated stamp ('checked 23 Oct 2026') is somewhat tangential but still relevant setup context, so it is only mildly wasteful.

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, non-mutating guidance tool with no output schema, the description covers what it returns, its side-effect profile, and the prerequisite server configuration. The one gap is that it does not characterize the return payload's shape or length, which would help an agent decide whether to call it or go straight to the browser tools.

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 no parameter semantics to explain and the baseline of 4 applies. The description correctly implies the call is argument-free by framing the output as procedural instructions.

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 names a specific verb and resource (create lead in SuiteCRM) and immediately qualifies that the tool only returns step-by-step screens/buttons/fields rather than performing the action. This distinguishes it from the cotlet_browser_* siblings that actually execute the creation. The only weakness is the internal tension between the leading 'Create lead...' phrasing and the later 'opens nothing by itself', which an agent must read twice to reconcile.

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 does route the agent onward, explicitly naming the cotlet_browser_* tools as the means to actually perform the creation, which is genuine usage guidance. However it gives no guidance on when to prefer this over siblings like suitecrm_convert_lead or suitecrm_list_leads, and no explicit when-not-to-use conditions.

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