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

Annotations already declare readOnly/idempotent/non-destructive, but the description adds meaningful context beyond them: it states the tool 'opens nothing by itself' and returns screens, buttons, and fields rather than acting. That distinction between a guide and an executor is exactly the kind of behavioral disclosure annotations cannot express. It stops short of describing output format or length, so not a 5.

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 clarification (returns instructions, then use browser tools) is stated early and earns its place. The trailing sentence about SysAid's Connect API and the absence of an official MCP server, complete with a 'checked 23 Oct 2026' date, is tangential justification that dilutes focus without helping the agent invoke this tool.

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, read-only guidance tool with no output schema, the description covers what the agent needs: what it returns (screens, buttons, fields), what it does not do (opens nothing), and the next tool family to use. Only the absence of any success/edge-case caveats keeps it from being fully complete.

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 meaning to add; the baseline for a parameterless tool applies. The description appropriately spends no words on inputs and instead explains the call's role in a two-step workflow.

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 definition names a specific verb and resource (add note in SysAid) and, importantly, clarifies that it returns a step-by-step walkthrough rather than performing the write. The opening sentence ('Add note in the user's own SysAid account') initially reads like a mutating action, so the true guidance-only nature only becomes clear in the second sentence — a small drag on clarity.

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 route the agent forward by naming cotlet_browser_* tools in the user's SysAid Cloud Browser as the execution step, which is real workflow guidance. However, it gives no explicit when-not guidance, no mention of alternative ways to add a note (e.g., the Connect API it cites), and no prerequisite conditions such as required permissions or an open browser session.

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