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

readOnlyHint=true already covers the safety profile, yet the description adds substantial behavior: result composition differs by authentication mode, expired drops carry `expired: true` and are reactivatable by their owner, delegated entries include the caller's role, and management tokens are never persisted server-side. This is exactly the kind of context annotations cannot express.

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?

It front-loads the core intent in the first short sentence, then packs the qualifiers afterwards. The second sentence is long and parenthesis-heavy, which slows parsing, but nearly every clause carries real information, so the density is mostly earned.

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 zero-parameter read tool with no output schema, the description does the important work of explaining what comes back in each auth mode and the meaning of the `expired` and `delegated` fields. It stops short of covering ordering, pagination, or limits, which an agent might still need for large accounts.

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-based baseline applies and there is nothing for the description to disambiguate. It sensibly spends its words on result semantics instead of parameter explanation.

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 and resource ('List your drops') and immediately scopes it: LIVE drops on the account, recently expired ones flagged `expired: true`, and delegated apps under `delegated`. It also distinguishes itself from siblings by naming dropyour_delete as the removal path and dropyour_delegate as the delegation context.

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 explains the two operating modes (account token vs anonymous session) and mentions sibling tools for adjacent actions, which effectively tells an agent when results will be broad vs narrow. However, it never explicitly says when to choose this over dropyour_list_versions or dropyour_records_list, so the comparison guidance is implied rather than stated.

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