CPersona

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

Annotations declare readOnlyHint=true. Description adds useful context that episodes are 'archived' (historical) and intended for 'dashboard display', but omits pagination behavior, ordering, or data completeness guarantees.

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?

Single sentence of nine words. Action-fronted with zero redundancy. Every word earns its place regarding scope and purpose.

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?

Appropriately complete for low-complexity tool (2 simple parameters, read-only). No output schema exists but tool name and 'list' verb make return value reasonably inferable; safety profile covered by annotations.

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?

Schema description coverage is 100% (agent_id and limit fully documented), establishing baseline 3. Description mentions 'for an agent' reinforcing agent_id semantics but adds no syntax, format, or dependency details beyond schema.

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?

Uses specific verb 'List' and resource 'archived episodes' with scope 'for an agent'. Qualifier 'archived' distinguishes from sibling 'delete_episode', though lacks explicit differentiation from 'list_memories'.

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?

Provides implied context 'for dashboard display' suggesting UI use case, but lacks explicit when-to-use guidance or comparisons to sibling alternatives like 'list_memories' or 'archive_episode'.

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