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

Annotations are not provided, so the description carries the burden. It discloses the tool is read-only implicitly (returns a full record), but doesn't state whether it's a read operation, potential errors, or network implications. There's no destructive or write implication, but the description doesn't explicitly confirm safety. It adds field context (what the record contains) beyond the schema, which is useful.

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 description is a single concise sentence that is front-loaded with the core purpose and then enumerates the fields. There is no waste, and it efficiently summarizes the returned record. However, it could be slightly more structured with a colon or bullet list, but the current form is acceptable.

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 tool's simplicity (one parameter, no output schema, no nested objects), the description is quite complete. It tells the agent what the tool returns (fields are listed) and which fleet to specify. The absence of an output schema is mitigated by listing the fields. Missing details like authentication or errors are not critical for such a straightforward read 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% (the single parameter 'fleet' is documented with an enum and description). The description does not add any new meaning about the parameter beyond what the schema provides. Baseline 3 is appropriate because the schema already covers the parameter fully.

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 it returns the full record for one fleet, with a specific list of fields (root, region, slot range, index, catalog, Card URL pattern). It distinguishes from sibling list_fleets (which lists fleets) and get_fleet_stats (which provides stats), though it doesn't explicitly name them. The verb 'Get' and resource 'one fleet' are clear.

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 implies when to use this tool: when you need the full record for a single fleet, as opposed to listing fleets or getting stats. However, it doesn't provide explicit when-not conditions or alternative tool names. There's no mention of prerequisites or use cases beyond that.

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