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

Goes well beyond the annotations by disclosing the lifecycle ('the upload becomes a DRAFT'), the required confirmation before publishing, and the failure fallback ('if no box appears, give the owner the link in this tool's result'). Annotations only cover the generic safety profile (openWorldHint, destructiveHint=false), which the description enriches with real workflow state.

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 tight sentences, front-loaded with the action and immediately followed by the usage rule and the draft/publish consequence. No 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?

No output schema exists, yet the description covers what the agent needs: the draft semantics, the required publish step, and the fallback when no upload box renders. Nothing essential for correct invocation 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 coverage is 100%, so the single optional 'category' enum is fully documented in the schema, including the hint to use my_photo_coverage for gap suggestions. The description adds no meaning about the parameter itself, which is the expected baseline when the schema does the work.

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 — 'Open an upload box in the conversation' — and scopes the flow precisely (photo from phone/computer to a Google listing). An agent can distinguish it from the sibling propose_photo without opening either schema.

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?

Explicitly says when to use it ('whenever the owner wants to add a photo') and when it does not apply ('a photo they paste into the chat cannot be sent to Google directly'). It also routes to the follow-up tool (publish_change) with the condition 'only when they say yes'.

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