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

Annotations already declare readOnlyHint and idempotentHint, so safety is covered. The description adds useful return-content context (bay count/capacity, deployed count, bandwidth usage, summary per drone), but doesn't mention pagination, rate limits, or freshness. Given annotations carry safety, a 3 is fair.

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?

Front-loads the core purpose, then the scope and alternative in parentheses. The nested parentheses with return summary plus sibling pointer are slightly dense but earn their 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?

No output schema, so it helpfully describes the return contents (counts, bandwidth, per-drone summary) and points to get_drone for full detail. A 1-param read tool needs little more; missing only edge cases like empty fleet or pagination.

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?

Only one parameter (session_id) and schema coverage is 100%, so the schema fully documents it. The description adds nothing about session_id nor compensates with parameter meaning; baseline 3 is appropriate.

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+resource ('List all your drones') and immediately clarifies scope (bay and deployed) while naming the sibling get_drone as the alternative for single-drone detail. An agent can distinguish this from get_drone without opening either schema.

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?

Explicitly routes detail-seekers to get_drone, giving a clear alternative. It doesn't state when-not to use (e.g., for drone actions like deploy/recall), but the guidance is concrete and actionable.

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