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

Annotations declare readOnlyHint=false, idempotentHint=true, and destructiveHint=false; the description aligns with these by disclosing that it persists a context revision (a mutation). It adds meaningful context beyond the annotations by clarifying the return substance: 'This retrieves documents, not server-generated prose.' It does not cover auth or limits, but adds real behavioral value.

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, front-loaded sentences with no waste. The purpose is stated first, followed by an important output clarification, then the routing instruction. Every sentence earns its place.

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?

There is no output schema and this is a mutating tool, so the description carries burden; it does explain that output is documents and that a context revision is persisted, which is helpful. However, with 40% schema coverage and no parameter guidance for query/title/maxTokens, an agent still lacks enough to call it correctly in all cases.

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 40%, so the description is expected to compensate for undocumented parameters. It says nothing about query, title, or maxTokens, leaving three of five parameters semantically unexplained in both description and schema. The description adds no parameter meaning beyond the 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?

The description states a specific dual verb+resource: 'Retrieve sourced business context for a dossier' and 'persist a reusable context revision.' It also distinguishes this from helvabase_read_context by naming it as the follow-up step. Clear purpose, though it does not differentiate from other retrieval-adjacent siblings like preview_sources.

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 gives a workflow hint ('Next call helvabase_read_context') that implies when this tool fits in a sequence. However, it offers no explicit when-to-use vs alternatives, no preconditions, and no exclusions. Usage is implied by sequencing rather than stated.

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