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

Annotations already declare readOnlyHint=true, idempotentHint=true and destructiveHint=false, so the safety profile is covered. The domain note 'A group is not an approved claim' is a real value-add beyond annotations, but the instruction to 'omit knowledgeAssetId to create a group' introduces write-flavored behavior on a tool annotated as read-only and refers to a parameter absent from the schema, creating confusion rather than clarity.

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?

Three short sentences, front-loaded with the listing purpose, which is reasonable structure. However, the final clause does not earn its place because it is misleading about the tool's read-only nature and about the available parameters.

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 list tool with no output schema, the description should convey what the returned groups look like (IDs, names) and how pagination behaves; it conveys neither. The presence of annotations lightens the safety burden but not the result-shape burden, and the misleading create clause leaves the agent with an incomplete and partially incorrect picture.

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 coverage is only 33% (only projectId is documented), so the description is expected to compensate and does not. limit and offset are self-evident from their bounds/defaults, and the description instead references a nonexistent knowledgeAssetId, adding no meaning to any real parameter.

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 opening clause gives a verb plus a domain resource: 'List existing groups of governed company information.' But the resource term is abstract and the second half muddies what the tool actually is, describing a creation flow rather than listing. No sibling tool is named to disambiguate it from the ~130 other helvabase 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?

'Use its ID for a proposal' implies a downstream workflow, which is genuinely useful orientation, but no alternative tool is named and no when-not condition is given. It also references a 'knowledgeAssetId' parameter that does not exist in this schema, so the guidance cannot be acted on as written.

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