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

Annotations only declare idempotentHint and destructiveHint=false; the description adds substantive behavior beyond them: public switching triggers a stricter content re-scan and may be rejected, badge removal requires a Pro token, and empty strings clear fields. Auth and failure-mode context are disclosed rather than implied. It omits any note on response/confirmation behavior, which keeps it from a 5.

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-loaded with the core action, and every clause carries information (no filler). It is a single dense sentence with nested parentheses that makes scanning slightly harder, but nothing is redundant.

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 an 8-parameter mutation tool with no output schema and thin annotations, the description covers the highest-risk behaviors (public re-scan rejection, token requirements, badge gating) that an agent must know before calling. Gaps remain around tag replacement and scheduling interactions, but the critical decision points are present.

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 63% (8 params), so the description has real work to do and does it for the ambiguous ones: visibility is unpacked into 'private = link-only + noindex, public = indexable', expiration semantics and name-clearing are explained beyond the schema. It adds no meaning for tags, publishAt, or dropId, which are left entirely to the schema.

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 ('Change a drop's settings') and then enumerates exactly which settings: visibility, expiration, badge, private name. An agent immediately knows the scope. It does not differentiate itself from nearby siblings like dropyour_patch, dropyour_replace, or dropyour_publish, so it stops short of a 5.

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?

Gives conditional prerequisites ('badgeHidden — Pro account token required', 'With an account token, owned drops need no managementToken'), which is real routing/auth guidance. However, it never states when to prefer this tool over dropyour_patch/replace/publish for the same resource, so the when-to-use-vs-alternative question is left to inference.

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