list_all_monologues_for_a_character

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

No annotations are present, so the description carries the burden. It does disclose the matching precedence ('exactly first, then as a substring') and the exhaustive list scope, but it does not mention return format, result ordering/pagination, or limit behavior beyond what the schema already states.

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?

Two focused sentences, front-loaded with the main action and scope, with every sentence contributing concrete information. No filler or redundant restating of the schema.

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?

For a simple two-parameter list tool with full schema coverage, the description provides the essential invocation information: target character, matching semantics, and examples. It lacks return-shape/pagination details, but those are not strictly required to select and invoke the tool.

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%, so the baseline is 3. The description adds value by giving example values and explaining how the character parameter is matched (exact, then substring), which is not in the schema. The limit parameter gains no descriptive additions.

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?

Clear verb-resource pair: 'List every monologue spoken by a given character', with concrete examples. It is easily distinguishable from siblings like get_monologue or random_monologue, but the description does not explicitly differentiate itself from search_monologues, so it falls short of a 5.

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 context for using the tool is obvious from the purpose and examples: when you need all monologues for a specific character. It does not explicitly state when not to use it or point to an alternative sibling, though the exact-then-substring matching note provides useful selection/use context.

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