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

Beyond the readOnlyHint annotation, the description discloses that secret values in the auth config are always returned masked and never leave the server, which is important behavioral context. It also mentions the project context requirement, adding useful transparency beyond annotations.

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 compact, using just three sentences to cover purpose, filtering capability, masking behavior, and usage alternative. Every sentence contributes meaningful information with no redundancy or filler.

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 simple listing tool, the description provides sufficient context: what it returns, how to filter, a behavioral note on masking, and a prerequisite (project context). It does not require an output schema, so the lack of output details is not a gap.

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 only parameter, personaId, is fully described in the schema with its type, default, and meaning (Public Id Guid). The tool description merely repeats 'Pass personaId to get a single one', adding no new information beyond the schema, so it meets the baseline but does not enhance semantic understanding.

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 clearly states that the tool lists security personas for the active project and optionally retrieves a single persona by ID. It also differentiates itself from manage_persona, making its purpose unambiguous and distinct from sibling 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 explicitly says to use this tool for browsing personas and to use manage_persona for creating, changing, or deleting them. It also notes that project context is required, providing clear when-to-use guidance with an alternative.

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