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

Beyond readOnlyHint and openWorldHint=false, the description discloses critical behavior: photos can be ready, working, or failed; failed photos are refunded; previews appear only when no photo is working; and the tool may block up to 25 seconds before answering. This is exactly the kind of behavioral detail an agent needs to avoid misinterpreting a slow or partial response.

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?

The description is front-loaded with the core return shape and then adds polling behavior. It is dense but earns its length because the status, link, preview, and waiting semantics are all important. Minor improvement would be splitting the long sentence for readability.

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?

With no output schema, the description does the necessary work of explaining the return payload: photo ids, statuses, links, shoot page, and conditional previews. It also covers polling and wait behavior. The main gap is that shoot_id remains semantically undocumented, which matters somewhat for this tool.

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?

The single parameter, shoot_id, has 0% schema description coverage, and the description does not explain its expected value, format, or source. The phrase 'A shoot's photos' implies the tool is scoped to a shoot, but it adds no real meaning beyond the parameter name and 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?

The description clearly states the resource and the full returned content: a shoot's photos, each photo's id, status, app link, the shoot page, and previews of ready photos. It is specific enough to distinguish this from general sibling tools like list_photos, though it does not explicitly contrast itself with any sibling.

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 gives explicit operational guidance: call again until none is working, and tell the user how many are ready each time. It also explains the built-in 25-second wait while photos are working. It does not mention when not to use it or name a sibling alternative.

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