fleet_snapshot

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

With no annotations, the description carries the full behavioral burden but discloses almost nothing. 'Get' implies a read, yet there is no statement about point-in-time semantics, freshness, permissions, or scope (whole fleet vs. one). Those gaps are exactly what an agent needs for a fleet-wide tool.

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?

A single short sentence, front-loaded with the verb and the enumerated resources. It is efficient with no filler, though its brevity reflects under-specification rather than tight editing.

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 parameters, no annotations, and no output schema, so the description must explain the return surface and usage context, and it does not. An agent does not know the snapshot's shape, granularity, or freshness, which matters for a fleet-state tool with this many siblings.

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 the schema baseline of 4 applies. There is nothing for the description to clarify regarding inputs, and it does not misrepresent the no-arg signature.

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 verb (Get) and three resources (drones, capacity, task state), so the agent knows the domain. However, 'capacity' and 'task state' are vague, and nothing distinguishes this fleet-wide snapshot from siblings like task_status or task_logs, which also surface task state. Purpose is readable but not sharply differentiated.

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?

No when-to-use guidance and no mention of alternatives. An agent cannot tell from the description whether fleet_snapshot should be preferred over task_status or dispatch_pending when it needs drone/task information. Usage is only weakly implied by the name.

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