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

Annotations already declare readOnlyHint, idempotentHint, and non-destructive behavior, so the bar is lower. The description adds domain-specific behavioral context: the actual policy chain a dossier must satisfy and the explicit statement that this read cannot mutate policy, which meaningfully informs the agent beyond the structured hints.

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 tight sentences with the core action front-loaded and no filler. The closing line reaffirms read-only semantics already implied by annotations, which is mildly redundant but very short.

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 read-only inspection tool with full schema coverage and no output schema, the description omits what the inspection returns (policy steps, satisfied vs outstanding requirements, per-step status). That gap is minor given the annotations, but it leaves the agent guessing at the response shape.

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?

Single required projectId at 100% schema description coverage; the schema already explains it is a Helvabase project/mapping ID from list or create dossier and never a local path. The description adds nothing further about the parameter, so the baseline 3 applies.

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?

Clear verb+resource: 'Inspect this dossier's server-required BID steps' tells an agent it is a read of bid policy for a specific dossier. It does not, however, differentiate itself from close siblings such as helvabase_read_bid_method, helvabase_request_bid_decision, or helvabase_confirm_bid_decision, so the boundary has to be inferred.

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 implies when the policy matters by naming the gating requirements (qualification, exact human bid decision, current clear control report) before final review or submission. It never states when to call this tool versus reading bid method or requesting/confirming a decision, so usage is only implied.

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