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

No annotations exist, so the description carries the burden: the verb 'List' makes the read-only nature evident, it declares the auth scope (authenticated user's characters), and it explains the meaning of the `loraReady` field in relation to `useLora: true`. It stops short of describing the full shape of a returned character or any pagination/empty-state behavior.

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?

Three short sentences, front-loaded with purpose, then the field that drives a downstream decision, then the negative constraint. Nothing is redundant and the constraint is not buried.

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 no output schema, the description must partially stand in for return values; it covers `loraReady` and `characterId` but not the other fields a character entry likely carries. For a zero-parameter read tool this is nearly sufficient, but a brief note on the other returned fields would close the gap.

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?

The tool takes zero parameters, so there is nothing for the description to disambiguate; baseline 4 applies. The description instead spends its words on the return-derived `characterId` value the caller needs downstream.

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?

Specific verb ('List') plus scoped resource ('the authenticated user's existing characters'), with a parenthetical defining what a character is ('AI influencers'). It also positions itself against the generate_* siblings by explaining that its output feeds their characterId parameter.

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?

Explicitly states the condition that selects this tool ('so you can pick a characterId for the other generation tools') and adds a hard exclusion: there is no character-creation tool, so creation must happen in the RYLA app. Both when-to-use and when-not-to-use are covered.

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