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

This is an annotation contradiction. The annotations declare readOnlyHint=true, but the description describes a mutation ('Set or clear a display name'). This directly contradicts the read-only annotation. Even though the description provides useful behavioral details (max length, visibility, clearing), the contradiction is a serious inconsistency, likely confusing the agent about whether this tool modifies state.

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 sentence, which is efficient, but the parenthetical is rather dense with multiple clauses and details. It is still concise and all information is relevant, so it earns a 4 rather than 5.

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?

The description covers the core behavior (set/clear), ownership requirement, character limits, visibility, and how to clear. For a simple 3-parameter tool with no output schema, this is quite complete. The only significant gap is the annotation contradiction, but that is a separate issue; the description's own content is sufficient.

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 coverage is 100%, so all three parameters are described in the schema. The description adds some extra context about the name (max 32 chars, same rules as ship names, pass empty to clear), which mostly mirrors the schema's parameter descriptions. It doesn't add significant new parameter-specific meaning 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 the tool's action: 'Set or clear an optional display name on a drone you own.' It specifies the resource (drone) and distinguishes it from sibling tools like name_ship (which handles ships). The scope (ownership) and capability (set or clear) are explicit.

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 clear context for when to use the tool: to set or clear a display name on a drone you own. It mentions the name is optional, not unique, and not visible to others, which implies it's for personal convenience. However, it does not explicitly contrast with alternatives like name_ship, so it doesn't fully satisfy the 'when-not' dimension.

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