Strings

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description adds the useful disclosure that items carry byte offsets and classification tags (url, path, email, ip, format, secret-ish, base64-ish). It says nothing about filtering/pagination behavior, which is where the real behavioral risk of a large output lies.

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 dense fragment with zero filler and the tag vocabulary front-loaded. The tradeoff is that it reads as a label rather than an instruction, but nothing is wasted.

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?

With 8 parameters, no output schema, and pagination controls (limit, offset, maxBytes with truncation semantics), the description says nothing about how results are paged or truncated or what a caller should expect back. The schema handles the mechanics, but the description leaves the agent without an operational picture of this tool.

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 coverage is 75%, so the schema already carries most parameter meaning. The description only reinforces the utf16 toggle and names the tag vocabulary that the `tag` parameter filters on, but adds no format, range, or interaction details for limit/offset/maxBytes/minLength.

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 names the resource (printable ASCII / UTF-16LE strings with offsets) and the tag taxonomy, so an agent can infer extraction of strings from a target. But it is a noun fragment with no verb and no differentiation from siblings like hexvero_bytes or hexvero_analyze, which also operate on target content.

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 guidance on when to use this instead of hexvero_bytes, hexvero_analyze, or hexvero_unknowns. The agent must infer usage purely from the tag list, and there are no stated preconditions (e.g., that targetId must come from hexvero_open, which only appears in the schema).

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