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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=true, so the safety profile is covered. The description adds only the endpoint path and the 'currently blocks' state; it discloses nothing about pagination, result volume, or auth requirements, leaving the behavioral bar minimally met.

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 short fragments with zero filler, and the resource description is front-loaded ahead of the endpoint. 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?

For a single-parameter read-only list tool with annotations covering the safety profile and no output schema, the description is essentially sufficient. It could optionally describe the returned fields, but nothing required for correct invocation is missing.

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%, so server_id is fully documented in the schema (referencing runcloud_list_servers). The description adds no parameter detail beyond the phrase 'on a server', so the baseline 3 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?

States a specific verb (list) and resource (IPs Fail2Ban currently blocks on a server), with the underlying endpoint GET /servers/{id}/security/fail2ban/blockedip. It is clearly distinct from generic siblings like runcloud_list_firewall_rules by naming Fail2Ban, though it does not explicitly contrast with them.

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?

Usage is only implied (security inspection of blocked IPs on a server). There is no explicit when-to-use guidance and no mention of the closest sibling runcloud_list_firewall_rules, so the agent must infer the boundary between Fail2Ban blocks and firewall rules.

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