Browse Fashio's ready-made photoshoot library

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

With no annotations, the description carries the behavioral disclosure burden. It does add useful context: this is a read-only browse of curated, not user-owned, content. However, it does not disclose pagination behavior, response shape, filtering semantics, or any side effects—though 'Browse' implies a safe list operation.

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 a single focused sentence with no filler. It front-loads the core purpose, uses an em-dash for the key exclusion, and ends with a practical workflow note. Every clause earns its place.

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?

Given 12 parameters, no annotations, and no output schema, this description is not complete enough. It orients the agent to the tool's purpose and relationship to siblings but does not explain filter meanings, paging via startAfter, defaults, or what the response contains, leaving significant room for incorrect 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 only 17%, so the description must compensate for undocumented parameters, but it does not. It explains the structure of the catalogue but gives no guidance for mood, sort, type, limit, gender, palette, setting, category, lighting, or featuredOnly. The example's structural hint is too indirect to count as parameter semantics.

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 action ('Browse') and a specific resource: Fashio's curated ready photoshoot catalogue, including composition details (one model + one venue + N pinned poses). It explicitly distinguishes itself from list_template_sets, making sibling differentiation immediate and unambiguous.

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 explicitly says this is NOT for the caller's own saved presets and points to list_template_sets as the alternative for those. It also recommends pairing with create_catalog_job, giving a clear workflow context for when to use this tool.

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