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

Annotations already declare readOnly, idempotent, non-destructive, closed-world behavior, so the safety profile is covered. The description adds that the record is a documented/aggregated profile, but says nothing about coverage gaps or empty results for low-profile talent, which is the main behavioral surprise an agent could hit.

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?

Purpose is front-loaded in the first clause, followed by a compact field inventory and a short input instruction. The field list is dense but earns its place as a scannable summary; no filler sentences.

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 and annotations covering safety and idempotency, the description need not explain return structure; the field inventory gives enough for selection and the slug-source instruction closes the loop. Only the absence of guidance on empty/sparse records keeps it from a 5.

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 already explains that slug comes from search_fashion_records and may also be a full tectova.com/talent/ URL. The description only restates the slug provenance, adding no new syntax or format detail beyond the schema, so baseline 3 applies.

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: a talent's documented runway record on Tectova, with the exact scope enumerated (Big Four count, seasons, top houses, per-season rows, agencies, honours, collaborators). This clearly separates it from get_brand_runway_history, get_show_cast, and search_fashion_records.

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 closing sentence establishes the prerequisite workflow by telling the agent to obtain the slug from search_fashion_records, which is a genuine routing hint among siblings. It does not, however, state when not to use it (e.g., when a brand-level history is wanted instead).

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