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

Annotations already declare readOnly, idempotent, non-destructive, closed-world behavior, so the bar is lower, and the description still adds real context: it returns how-to text rather than performing anything, and "opens nothing by itself" reinforces the no-side-effect guarantee. The note that Simpro has a REST API but no official MCP server explains why the browser-detour pattern exists, which an agent cannot infer from annotations alone.

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 content is front-loaded and short, but the opening clause duplicates the name/title and "from ChatGPT, Claude or any AI agent" is promotional filler. The closing sentence about Simpro's REST API and the "checked 17 Oct 2026" date is tangential to invoking this tool, so not every sentence earns its place.

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 zero parameters and no output schema, the description carries the burden of saying what comes back, and it does: step-by-step instructions rather than data or actions. It also explains the two-step pattern with the browser tools, which is enough for an agent to call it correctly. It could be more complete by indicating how the instructions map to a specific schedule or date.

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 no parameter semantics to explain and the baseline of 4 applies. Nothing in the description misrepresents or adds confusion about inputs.

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?

"Check schedule" largely restates the name and title and never says which aspect of the schedule is being checked (upcoming entries, availability, conflicts). The second sentence rescues it by specifying the actual output: step-by-step Simpro instructions with screens, buttons and fields. It also implicitly contrasts itself with the cotlet_browser_* tools, but does not differentiate from Simpro siblings such as simpro_list_jobs.

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 clear workflow: call this to get instructions, then execute them with the cotlet_browser_* tools in the user's Simpro Cloud Browser. That is concrete when-to-use guidance tied to named alternatives. It stops short of explicit exclusions (e.g., when to prefer a direct API-style sibling instead), so it is not a 5.

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