list_personalities

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

Without annotations, the description carries full burden. It discloses that personalities have 'tempo_sweet_spot' and 'tempo_range' and that beyond that range the generators emit warnings and scale density/swing. However, it does not explicitly state that the operation is read-only or idempotent, though it can be inferred.

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 well-structured with markdown sections, clear role groupings, and front-loaded purpose. Every sentence adds value, and the length is appropriate for the information conveyed.

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 tool with no input or output schema, the description adequately covers what it returns (list grouped by role, with tempo information). It could have explicitly stated the return format (e.g., array of objects) but is sufficiently complete for its purpose.

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 input schema has zero parameters, so the description does not need to add parameter semantics. The baseline score for 0 parameters is 4, as per guidelines.

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 explicitly states 'List every available personality style profile, grouped by role.' It uses a specific verb and resource, and distinguishes from sibling tools like add_personality and add_personality_solo by explaining how the output 'key' is used as an argument for those tools.

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 provides clear context on when to use this tool: to list personalities and obtain the key for other tools. It includes roles and example personalities, but does not explicitly state when not to use it or alternative tools; however, the context is sufficient for an AI agent.

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