get_persona_summary

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

Annotations already declare the tool is read-only, idempotent, non-destructive, and closed-world. The description adds useful scope by stating it returns a compact profile and index coverage and explicitly excludes raw conversation history, but it does not provide additional behavioral details such as permissions, rate limits, or what 'index coverage' entails.

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, front-loaded sentence that states the return content and the key exclusion without any wasted words. It is optimally sized for a zero-parameter read operation.

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?

Given the low complexity (no parameters), the presence of an output schema, and annotations that cover the safety profile, the description provides enough context to invoke the tool correctly. The main omission is sibling differentiation, which is already reflected in the usage-guidelines score.

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 tool takes zero parameters, so there are no parameter semantics to describe. Per the rubric, zero parameters establish a baseline of 4, and the description needs no further parameter guidance.

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 names a specific verb ('Return') and resource ('compact profile and index coverage'), making the tool's output clear. However, it does not differentiate from similar-sounding siblings like get_person_style or get_style_profile, so an agent cannot easily tell when to prefer this tool over them.

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 includes a negative scope statement ('without raw conversation history'), which hints at when not to use it, but it offers no explicit when-to-use guidance and never names alternatives. An agent must infer its role among five sibling tools with overlapping profile/style purposes.

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