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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=false, so the safety and side-effect profile is fully covered by structured data. The description adds only mild context: that results are dossier-scoped (implying the required projectId) and include buyer feedback. It says nothing about pagination behavior or result shape, which is acceptable given the annotation coverage but not particularly additive.

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?

A single front-loaded sentence with no filler, which is appropriate for a simple read tool. It is efficient, though its brevity shades into under-specification rather than disciplined conciseness.

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 tool with three parameters, no output schema, and low schema-description coverage, an agent gets no indication of what an 'outcome' record contains or how pagination works. The safety profile is covered by annotations, but the read contract itself is left to discovery.

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 33% – projectId is documented (with a note that it is a Helvabase ID, not a local path), but limit and offset have no descriptions and the description text says nothing about pagination, ordering, or how many outcomes are returned by default. The description does not compensate for the low coverage, so it adds essentially 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?

States a specific verb (read) and resource (recorded outcomes and buyer feedback) scoped to a dossier. It is clear on its own, but it does not distinguish itself from the sibling write counterpart helvabase_record_outcome or from other read tools like helvabase_output_download; the word 'outcomes' is left somewhat generic.

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?

There is no when-to-use guidance, no preconditions, and no mention of alternatives such as helvabase_record_outcome (the write path) or other dossier read tools. The agent must infer when this tool is appropriate from the name alone.

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