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

The annotations already declare readOnlyHint=true and destructiveHint=false, and the description reinforces this with the concrete statement that the tool 'opens nothing by itself' and that execution must be done through browser tools — an important behavioral fact beyond the annotation. It also explains why the official API is not an option (Pro-plan-only, no official MCP server). It stops short of describing the shape or length of the returned instructions.

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 instruction is compact and the workflow sentence is front-loaded, but 'from ChatGPT, Claude or any AI agent' is filler, and the trailing API/plan note, while useful motivation, delays the key caveat that the tool performs no action. Leading with the guidance-only nature would be far more efficient.

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 the essential workflow and the API constraint. It leaves a real gap around inputs — how the specific job and target status are identified when there are no parameters — which matters for an agent deciding whether it has enough context to call it.

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 schema baseline is 4 and there is nothing for the description to disambiguate. The absence of any input is still worth noting: the description never explains how the target job or desired status is conveyed, presumably from conversation context, which an agent must infer.

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 opening sentence says 'Update job status in the user's own Service Fusion account', which reads as if the tool performs the mutation, and only the second sentence reveals that it actually returns step-by-step instructions and 'opens nothing by itself'. Once read in full the purpose is clear, but the first line points an agent in the wrong direction, and nothing distinguishes this from the sibling cotlet_app_guide.

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?

The description does give a sequencing rule — call this to get the screens/buttons/fields, then perform the change with the cotlet_browser_* tools — which is genuine usage guidance. It offers no exclusions, though: it never says when to prefer cotlet_app_guide or cotlet_apps, nor what to do if the user's plan or the Cloud Browser is unavailable.

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