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

With no annotations provided, the description carries the full burden of behavioral disclosure. It discloses that full prompts unlock after bootstrap_session, which is useful context, but it does not mention authentication, rate limits, or the behavior before bootstrap_session. This adds some transparency but leaves significant gaps.

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 that front-loads the action and resource, with every word contributing meaning. There is no wasted text, and the structure is perfectly appropriate for a simple list tool.

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 adequately covers the operation, returned fields, and a key behavioral dependency. However, it does not clarify what happens before bootstrap_session (e.g., whether results are partial or error), which would make it fully complete.

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 properties, and the baseline for 0 parameters is 4. The description mentions the return fields but no parameter semantics are needed, so the baseline 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 uses the specific verb 'List' and specifies the resource 'persona' along with the returned fields (slug, title, role). This clearly distinguishes it from sibling tools like get_persona, which fetches a single persona, making the purpose unambiguous.

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 implies that full prompts are available after bootstrap_session, but it does not explicitly state when to use this tool versus alternatives such as get_persona or other list tools. The usage context is present but not fully elaborated with exclusions or alternative recommendations.

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