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

Annotations already declare readOnlyHint=true and destructiveHint=false, and the description is consistent with that while adding real value: it discloses that the return payload is procedural guidance, not data, and that no action is taken. It does not describe the structure or granularity of the returned guide beyond 'screens, buttons, fields'.

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 is stated early, which is good, but the opening clause 'from ChatGPT, Claude or any AI agent' is promotional filler and the closing note about Officient's API and a check date adds little decision value. Roughly a third of the text could be removed without losing meaning.

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?

There is no output schema, so the description carries the burden of explaining what comes back, and it only loosely characterizes the result as step-by-step screens, buttons and fields. For a parameterless tool this is serviceable, but an agent cannot predict the shape or scope of the returned guide.

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 schema applies.

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 name and title say 'List colleagues', but the description reveals the tool returns step-by-step instructions (screens, buttons, fields) rather than colleague data. That key distinction is stated, yet the mismatch with the name forces the agent to read the body to understand what actually happens. It also does not distinguish itself from sibling list tools such as officient_list_colleague_absences.

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 explicitly prescribes the workflow: get the guide here, then execute it with the cotlet_browser_* tools in the Officient Cloud Browser. It also states a clear exclusion of scope by saying it 'opens nothing by itself'. It stops short of saying when a different entry point (e.g. cotlet_app_guide or a sibling list tool) would be preferred.

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