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

Annotations already declare readOnlyHint=true, openWorldHint=false, destructiveHint=false, covering the safety profile. The description adds valuable behavioral context: what the result set contains (built-in + custom) and the runnable_id field, which is the actionable payload.

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 tightly written sentences with no waste; the primary purpose is front-loaded and the follow-up sentence is the actionable link to downstream tools.

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?

No output schema exists, and the description compensates by naming the key field returned (runnable_id) and how it is consumed. It leaves pagination/count behavior implicit, but for a read-only list tool this is minor.

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?

There is effectively one optional parameter (context), and schema coverage is 100%, so the schema fully documents it; zero required params sets a higher baseline. The description adds no parameter detail, but none is needed since the field is self-explanatory.

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?

States a specific verb (List) and resource (end-user personas) and further scopes it as built-in personas plus the authenticated user's saved custom personas. An agent can distinguish it from related sibling tools like run_persona_review and run_persona_consensus.

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 links the output (runnable_id) to its downstream use as the persona argument for run_persona_review or run_persona_consensus, making the workflow clear. It does not spell out explicit 'when not to use this' cases, but the context is unambiguous.

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