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

Annotations already declare readOnlyHint, idempotentHint and openWorldHint=false, but the description adds genuinely new context: the tool 'opens nothing by itself' and returns procedural instructions (screens, buttons, fields) rather than performing the action. That distinction is the single most important behavioral fact about this tool and it is disclosed clearly.

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 first two sentences are well-structured and front-load the workflow, but the final sentence about Simpro's REST API and the absence of an official MCP server is filler that does not help the agent call the tool, and it carries an odd future date ('17 Oct 2026') that adds noise.

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?

With no parameters and no output schema, the description carries the burden of explaining what comes back, and it does so ('how to do it in Simpro step by step (screens, buttons, fields)'). Combined with the pointer to the cotlet_browser_* tools, an agent has enough to act correctly; only the misleading lead sentence and the irrelevant API aside weaken 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 there is nothing for the description to disambiguate. Baseline for a parameterless tool applies, and the schema correctly enforces additionalProperties=false.

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 ('List jobs in the user's own Simpro account') reads as if the tool lists jobs, and only the second sentence reveals the actual behavior: it returns step-by-step instructions rather than data. The clarification is present and names the follow-up browser tools, but the name/title mismatch forces the agent to read past a misleading first line before understanding the tool.

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 state the workflow pattern explicitly ('opens nothing by itself; then do it with the cotlet_browser_* tools'), which tells the agent this is a precursor step. However, it gives no guidance on when to prefer this over the simpro_* siblings that appear to act directly on Simpro data, and no exclusions or prerequisites are stated.

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