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

Annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=true, and destructiveHint=false, so the safety profile is covered. The description adds useful domain context about governed information and the group-vs-claimed-claim distinction, but does not disclose additional behavioral traits such as pagination or result completeness. This is acceptable given annotation coverage, so a mid-score is appropriate.

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 appropriately sized: three sentences, each carrying distinct meaning. The core action is front-loaded, followed by entity clarification and downstream usage. No redundant phrases 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 list operation with annotations covering the read-only safety profile, the description is mostly adequate. However, it references a parameter (knowledgeAssetId) that is not in the schema and does not explain expected return values or result ordering. The domain clarification adds value, but the knowledgeAssetId discrepancy leaves a gap in completeness.

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 only 33%, and the description does not explain any of the actual parameters (projectId, limit, offset). It mentions 'knowledgeAssetId' which is not present in the input schema, creating potential confusion about this tool's parameter surface. With low schema coverage, the description should compensate but does not.

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 a specific verb-resource pair, 'List existing groups of governed company information,' which clearly identifies the operation and scope. It also distinguishes the resource type by stating 'A group is not an approved claim,' helping to disambiguate from sibling claim-related tools even without naming 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 provides concrete context on how the tool's results are used: 'Use its ID for a proposal, or omit knowledgeAssetId to create a group from the reviewed evidence.' This gives an agent actionable guidance on when the returned IDs matter and how they relate to downstream proposal/creation actions, though it does not explicitly enumerate alternative listing tools.

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