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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, and the description reinforces this with 'opens nothing by itself', which is the key safety fact an agent needs before calling. It also characterizes the return value (screens, buttons, fields). It says nothing about whether the user's Simpro Cloud Browser must already be connected/open, which is the main remaining operational unknown.

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 front-loaded and useful, but the closing sentence about Simpro's REST API and the absence of an official MCP server ('checked 17 Oct 2026') is marketing context that does not help an agent decide or invoke. That tangent dilutes an otherwise tight definition.

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, no output schema and rich annotations, the description carries what is needed: what it returns, that it mutates nothing, and which tools to use next. The gap is preconditions (app/browser session setup for Simpro), which would matter for an agent orchestrating the follow-on browser steps.

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 and the baseline of 4 applies. It does not claim any inputs exist, keeping it consistent with the empty schema.

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 makes the actual behavior explicit despite the misleading 'add' verb in the name: it returns step-by-step Simpro UI instructions and 'opens nothing by itself'. That is a specific and checkable claim about what the tool does. It does not, however, state how this guidance tool relates to the sibling simpro_check_schedule or when a plain guide suffices.

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 names the follow-on path directly: 'then do it with the cotlet_browser_* tools in the user's Simpro Cloud Browser', which tells the agent this is the first half of a two-step workflow. It gives no explicit when-not guidance (e.g. when to use the Simpro REST API or another Simpro tool instead), so the exclusion side is missing.

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