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

Annotations already mark readOnlyHint=true, and the description adds non-obvious behavior: it reads the DROP's record rather than the running app, managementToken is not needed for owned drops with an account token, and view count is approximate. No contradictions.

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?

Three compact sentences with useful information front-loaded: fields first, auth nuance second, disambiguation last. No filler or repeated schema info.

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 2-param read-only tool with no output schema, the description lists expected return fields, handles auth guidance, and directs the agent to the correct sibling for live app state. Nothing needed to call it correctly is missing.

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 has zero description coverage, but the description partially compensates by explaining managementToken's role and when it can be omitted. However, it does not explain dropId beyond the tool name and requires the agent to infer it is the drop identifier; the coverage gap is not fully closed.

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 ('Get a drop's status') and enumerates the returned fields, which is enough to identify it. Explicitly distinguishes itself from dropyour_schedule by contrasting the drop record vs the running app, so an agent can disambiguate.

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?

Provides explicit selection guidance: the first sentence covers record-level info, and the second sentence determines when a token is needed; the final sentence names the sibling and condition ('for a graduated app's live state... call dropyour_schedule'). It is clear when to use this tool versus alternatives.

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