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

Annotations indicate readOnlyHint, openWorldHint, idempotentHint, and destructiveHint=false, but the description goes beyond this by explaining the division of labor: the assistant does the reasoning and writing, while Helvabase enforces governance. It also clarifies that no skill installation is required, which is useful for an agent deciding whether to invoke this tool. No contradiction with annotations.

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 concise, but the opening sentence is somewhat run-on. It front-loads the tool's purpose and then adds the context about no skill installation. The second sentence is slightly abstract but still relevant. It could be tightened, but it's not verbose.

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 has no parameters and no output schema, the description covers the essentials: what the method is, how it works (assistant reasons, Helvabase governs), and the key constraint (no skill installation). For a read-only, zero-parameter tool, this is sufficient for an agent to decide whether to call it.

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?

The tool has zero parameters, and the schema is empty (100% coverage trivially). The description doesn't need to explain parameters, but it adds context about the tool's operation and constraints, which is useful. Since there are no parameters, the description adequately fills the gap.

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 clearly states the tool's purpose: reading the BID response method and its specific steps (qualify, map evidence, select useful pieces, draft, correct, review, reuse). Despite the generic 'read' prefix, the description provides a specific resource and function, distinguishing it from sibling read tools like helvabase_read_qualification or helvabase_read_document_plan by describing the multi-step method.

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 explains that it works without installing a skill and that the customer assistant reasons and writes while Helvabase enforces governance. This gives some context for when to use it, but it does not explicitly state when not to use it or name alternative tools. The guidance is implicit rather than explicit.

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