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

Annotations already signal that this is a mutating, destructive, idempotent operation. The description adds useful context (retrieves documents, persists a revision, not server prose) but does not disclose what 'persist a reusable context revision' entails for existing revisions (e.g., overwrite, create new version, side effects). It does not contradict annotations, but it misses an opportunity to elaborate on the destructive behavior the annotations hint at.

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 three sentences, each earning its place: the core action, the clarification about what it returns, and the next-step pointer. It is front-loaded with the primary purpose and contains no 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?

Given the tool's complexity (5 parameters, no output schema) and the presence of annotations, the description gives a clear high-level duty and directs the agent to the next step. However, it omits important context: the exact nature of the persisted 'revision', whether it replaces or creates revisions, and any prerequisites (e.g., dossier must exist). These gaps matter for a mutating tool with destructiveHint=true.

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% (projectId and idempotencyKey have descriptions; query, title, and maxTokens do not). The description provides no parameter information whatsoever, so it fails to compensate for the schema's low coverage. An agent is left without clarity on the meaning of key inputs like 'query' or the effect of 'maxTokens'.

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 action ('Retrieve sourced business context for a dossier') and a distinct secondary action ('persist a reusable context revision'). It explicitly distinguishes the tool's behavior from related ones by noting 'This retrieves documents, not server-generated prose.' It also names the sibling tool to call next, making its role in the workflow unambiguous.

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 a sequencing hint ('Next call helvabase_read_context') but does not explicitly state when to use this tool over alternatives such as helvabase_prepare_client_file or helvabase_prepare_document_analysis. There are no exclusions or conditional pathways, so usage context is only implied.

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