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

Annotations already declare readOnlyHint=true, so the description doesn't need to repeat that. The description adds the endpoint and hints at monitors being CPU/disk-related, but does not disclose additional behavioral traits like rate limits or auth requirements. No contradiction.

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?

Two sentences, each serving a distinct purpose: first explains the tool's function, second provides the API endpoint. No redundant or unnecessary text. Front-loaded with the essential purpose.

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?

Given the absence of an output schema, the description could have provided more detail on return values or structure, but it adequately covers the purpose and parameters. With 100% schema coverage and a read-only annotation, the description is sufficiently complete for a straightforward list operation.

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?

Schema description coverage is 100% with descriptions for all four parameters. The description adds value by specifying that monitors include 'CPU/disk/etc.', providing domain context beyond the schema. However, it does not detail parameter formats or relationships beyond what the schema already provides.

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 clearly states 'List server monitors (CPU/disk/etc.)', specifying the verb (list), resource (server monitors), and scope. The title 'List monitors' is unambiguous. It distinguishes from siblings like forge_get_server or forge_list_servers by focusing on monitors.

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?

The description provides the API endpoint with placeholders, implying usage with organization and server IDs, but does not explicitly state when to use this tool versus alternatives or when not to use it. No exclusions or context for selection from siblings.

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