List selectable poses

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

No annotations are provided, so the description must carry the behavioral burden. 'Browse' and 'catalog' imply a read-only listing with no side effects, and linking to create_generation clarifies the output's role. However, it does not disclose auth expectations, pagination behavior, or the shape of what is returned, so transparency is only partial.

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?

One tightly worded sentence with the purpose front-loaded and no filler. It avoids repeating schema details and earns its place by supplying the integration context.

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?

This is a low-complexity catalog listing with two optional parameters fully documented in the schema. The description supplies the crucial integration context and enough of the selection purpose. Without an annotations block or output schema, a brief note on the returned values would have rounded it out, but nothing essential is missing for correct invocation.

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%, so the description need not restate parameter details. It adds the useful context that returned poses are meant for the `pose` field of create_generation, which meets baseline without adding extra syntax or format information.

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 ('Browse the catalog of poses') and ties it directly to a downstream use ('to use as `pose` in create_generation'). The resource is unambiguous, and among the list_* siblings this is the only pose-specific listing, so it stands apart without needing an explicit exclusion.

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?

Gives a clear context: this is the tool to browse pose values before calling create_generation. It does not name alternatives or say when not to use it, but the integration with create_generation is explicit enough to guide selection among sibling list tools.

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