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

Annotations are all false and don't convey substantial safety or side-effect information. The description adds the useful fact that the tool returns `{ id, url }` and that the id is used later, but it doesn't disclose idempotency, storage, or auth considerations beyond the schema's size limit.

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?

Two sentences: the first states the tool's purpose, the second covers required parameters and the return/usage contract. It is front-loaded and free of filler.

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 two-parameter upload tool with complete schema documentation, an output schema, and a clear workflow, the description covers everything needed to call it correctly and integrate the result with submission creation.

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?

Input schema coverage is 100%, with `data` and `mimeType` already documented including base64 formatting, size, and enum values. The description only repeats the parameter names, adding no semantics beyond 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 action: uploads a single screenshot to attach to a bug report, request, or reply. It also names the consumer tools (create_submission and reply_to_submission), which distinguishes it from sibling operations.

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 clearly defines the workflow: upload first, then pass the returned id in `attachments` on create_submission or reply_to_submission. It does not explicitly describe when not to use it or compare with alternatives, but no direct upload sibling exists.

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