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

The description goes well beyond the readOnlyHint annotation by detailing return scopes (server vs client-only), the exact shape of the response, and a critical security warning that returned data is not instructions. It also clarifies the managementToken requirement nuance, providing substantial behavioral insight not captured in structured metadata.

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?

Every sentence contributes value: purpose, return scope explanation, auth nuance, and a security warning. The structure front-loads the core function and then layers important caveats, all in a compact yet thorough format. No filler or repetition.

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 return format, scopes, auth requirements, and a safety warning, which is comprehensive for a read operation. The only missing piece is explicit parameter guidance, but the tool's simplicity and the clear purpose mitigate this. Given no output schema exists, the description compensates well by describing the response shape.

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?

With 0% schema description coverage, the description must explain parameters, but it only mentions managementToken in passing ('with an account token, owned drops need no managementToken') and does not describe dropId at all. The dropId pattern is in the schema but its purpose is left implicit, leaving the agent to infer meaning from the tool name. This is a notable gap given the schema provides no descriptions.

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 explicitly states the verb 'read', the resource 'a drop's app data', and elaborates on what that means (a JSON key/value snapshot mirroring the app's localStorage). It also differentiates from siblings like read_app_files and read_content by specifying 'app data' as the shared-memory state, making the tool's unique role 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?

It provides clear context for when to use the tool ('to answer questions about what the app holds') and explains the two possible scopes (server vs client-only). It does not explicitly name alternatives or when-not-to-use conditions, but the purpose is unambiguous enough to guide selection without confusion.

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