listAllHashes

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

With no annotations, the description bears full responsibility for behavioral disclosure. It only states the action (get) but does not specify whether it is read-only, whether pagination affects results, or the format of returned data. This is insufficient for safe invocation.

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 a single concise sentence, but it lacks structure and front-loading. It could be improved by briefly noting pagination or the expected output, without becoming 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 absence of annotations and output schema, and the presence of many sibling tools (e.g., getJsonSection_md5), the description does not provide enough context to understand what 'all report MD5 hash values' means—whether it lists all hashes across reports or within a single report, or the data structure returned.

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 input schema already describes both parameters (page and pageSize) with clear descriptions, achieving 100% coverage. The description adds no additional meaning, so a baseline score of 3 is appropriate.

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 gets all report MD5 hash values, using a specific verb and resource. It distinguishes from siblings like getJsonSection_md5, which likely retrieves a single MD5 for a specific scan, but could be more precise by mentioning 'list' instead of 'get' and indicating pagination.

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?

No guidance is provided on when to use this tool versus alternatives such as getJsonSection_md5 or getRecentScans. The description does not mention any prerequisites, contextual cues, or exclusions.

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