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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds useful behavior beyond that: pagination size ('50 per page') and the exact scope of returned fields, which tells the agent what a page contains.

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?

A single dense sentence that front-loads the payload description and ends with the input requirement — no filler. It is slightly crammed with enumerated fields, but every clause carries information the agent can use.

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 an output schema present, return structure needn't be spelled out, and the description covers scope, provenance of the input, and page size. Only minor gaps remain, such as whether an undocumented/empty cast is possible or how to tell when paging is exhausted.

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% and the schema descriptions already explain both `show` (path or full URL, with provenance) and `cursor` (next_cursor). The description's mention of 'a show path from get_brand_runway_history or get_talent_runway_record' largely duplicates the schema text, so it adds little beyond the baseline.

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+resource ('the documented cast of one runway show on Tectova') and enumerates the payload (house, season, city, date, design credits, models). It also distinguishes itself from the history/record siblings by naming them as the source of its input rather than as alternatives.

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 precondition: the show path must come from get_brand_runway_history or get_talent_runway_record. That routes the agent away from guessing paths, though it doesn't state any explicit when-not condition or contrast with search_fashion_records.

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