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

Annotations declare readOnlyHint=false, openWorldHint=true, idempotentHint=false and destructiveHint=false. The description usefully adds that this renders an interactive inline component where the user clicks to upload, which explains why it is not a read-only operation. It does not say whether the uploads go through the approval flow implied by the `swiftly_*` approval siblings, nor what the call itself returns.

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, zero filler, with the interactive behavior front-loaded ahead of the usage trigger. Slightly more compact routing guidance could have displaced nothing, but nothing is wasted.

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?

There is no output schema, so the description should carry the return behavior; it gestures at an inline gallery UI but not at what tool output the agent receives or how the subsequent upload is confirmed. With five parameters and a mutation-adjacent flow, the definition is adequate but leaves the post-browse sequence underspecified.

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 description coverage is 100% with 5 well-documented parameters including enums, so the schema carries the parameter burden. The description adds no syntax, default, or format detail beyond the schema — baseline 3 is appropriate.

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 states a specific verb and resource — 'Open a visual photo gallery inline in the chat' — plus the downstream effect of uploading favorites to WordPress. It is clear on its own, but it never distinguishes itself from the sibling `stock_photo_search`, which an agent could easily confuse with this tool.

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?

'Use this when the user wants to visually browse and choose photos' gives an implied trigger condition for the browse-and-pick case. However, it names no alternatives and offers no exclusion criteria against `stock_photo_search`, `swiftly_request_upload`, or `wp_upload_media`, so the routing decision is left partly to inference.

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