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

Annotations already declare readOnlyHint=true, idempotent, non-destructive, and closed-world; the description reinforces this with 'opens nothing by itself' and adds the useful disclosure that the response is a step-by-step walkthrough of screens, buttons, and fields. With no output schema, this return-value description carries real weight.

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 core behavior and return format are front-loaded, but the trailing note about Method CRM's official REST API and lack of an MCP server is tangential and the sentences are long run-ons joined by semicolons. It is informative but not tight.

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 guide tool, the description covers what it does, what it returns, and how to act on the result. It could say more about what user context the step-by-step assumes, but nothing essential to correct invocation is missing.

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 the baseline is 4. The description correctly implies no inputs are needed and does not invent parameters.

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 the resource (activity in the user's own Method CRM account) and clarifies that the tool itself does not create anything but returns step-by-step instructions. That distinction from the cotlet_browser_* siblings is explicit, though the name 'create_activity' vs. actual guide behavior creates mild initial ambiguity.

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 concrete workflow: call this to get the steps, then perform them with the cotlet_browser_* tools in the user's Cloud Browser. It does not explicitly say when not to use it or contrast it against other Method CRM siblings such as create_estimate, so it stops short of full routing guidance.

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