list_available_personas

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

No annotations are provided, so the description carries the full burden. The description is read-only in nature and mentions preset vs custom personas, but gives no context about return format, pagination, ordering, or whether custom personas include user-created ones vs system configurations.

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?

The description is a single concise sentence in Japanese, zero waste. It efficiently communicates the core purpose with the parenthetical clarifying scope (preset + custom).

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 zero-parameter list tool with no output schema, the description is adequate but minimal. It could benefit from describing what a persona includes or how the preset/custom split is represented, but the core retrieval behavior is clear enough for a simple list operation.

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?

No parameters exist, so the schema needs no documentation. With 0 parameters, the baseline is 4, and the description appropriately requires no additional parameter explanation.

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 states the tool retrieves available personas (preset + custom), which provides a clear verb+resource. It distinguishes from the sibling list_personas to some extent by noting it includes presets, but doesn't explicitly clarify what differentiates these two list functions.

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 description gives no guidance on when to use this tool versus the similar sibling list_personas. For an agent choosing between two list-persona tools, no differentiation or context is provided to help select the right one.

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