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

The description usefully confirms the read-only nature ('opens nothing by itself'), which corroborates readOnlyHint=true, and adds real context about Agile CRM's REST API availability and per-plan daily call caps. However it omits what the reply actually looks like beyond 'step by step' and gives no indication of any cost/latency for generating a browser-driven walkthrough. It adds value but not rich behavioral detail beyond 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 behavioral fact — that it returns instructions and performs nothing — is buried in the second sentence behind a marketing clause naming chatbots, and the third sentence about the official API and absence of an MCP server is contextual filler rather than call-relevant guidance. It is not egregiously long, but the front-loading is poor and at least one clause is expendable.

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, no-output-schema tool, the definition covers what matters: what it returns, that it mutates nothing, and which tools carry out the action. The remaining gap is that it never explains how the agent should convey the target contacts and campaign, which is non-obvious given an empty input schema.

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 empty, so there is nothing for the description to disambiguate; baseline 4 applies. The description does not explain how the tool knows which contacts or which campaign to walk the agent through, but with no parameters there is no schema semantics to add to.

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 second sentence states the actual behavior specifically: it returns step-by-step Agile CRM instructions (screens, buttons, fields) and performs no action itself, then hands off to the browser tools. This is clear enough to distinguish it from a true mutating 'add' tool, but the leading clause 'Add contacts to campaign' plus the marketing tail ('from ChatGPT, Claude or any AI agent') muddy the verb before the correction arrives, and it does not differentiate itself from guide-style siblings like agile_crm_add_contact_tags.

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?

Explicit sequencing is given: read the returned steps, then execute them with the cotlet_browser_* tools in the Agile CRM Cloud Browser. That routes the agent to the correct follow-on tools, though it never states when this tool should NOT be used (e.g., when a direct API-backed sibling would be preferable).

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