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

Beyond the readOnly/destructive annotations, it discloses licensing terms (Free Rehearsal License), the English-only constraint, that results are reading-only with no live voice reader or native opening link, that an empty list means no match, and the anti-hallucination rule 'never invent or cut text to meet a limit.'

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?

It is front-loaded with the positive use case before the exclusions, and every sentence carries information. It is dense with negative constraints across several sentences, but none are redundant with the schema or annotations.

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 5 optional params, an output schema, and read-only annotations, the description covers the remaining gaps an agent needs: licensing, language limitation, empty-result behavior, and the sibling handoff for reading a chosen piece.

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 all five filters (genre, locale, age_range, difficulty, max_duration_seconds) are already documented in the schema. The description largely restates the returned attributes rather than adding syntax or edge-case meaning beyond what the schema provides, so the 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?

The description opens with a specific verb+resource+scope: retrieving short original solo monologues for an actor, and enumerates the returned attributes (role, genre, age range, difficulty, duration, license). It explicitly separates itself from list_practice_scenes and routes to the sibling get_practice_monologue.

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 provides explicit trigger conditions (reading, memorization, cold read, non-commercial selftape practice), names the follow-up tool get_practice_monologue, and lists clear exclusions (two-person scenes, private audition sides, famous-play excerpts, translation, casting judgments, commercial rights).

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