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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It mentions 'input discarded' for some parameters, but it does not explain side effects, return values, or what 'Murmur hash hex length' means behaviorally. The description is too terse to disclose meaningful behavior.

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 extremely short, but it is under-specified rather than concise. It lacks a verb, object, and any explanation of the tool's function. The phrase 'input discarded' is confusing and does not earn its place.

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?

The tool has 9 optional parameters, no output schema, and no annotations. The description provides almost no context about what the tool does, what it returns, or how the parameters relate to the operation. This is completely inadequate for an agent to select and invoke the tool correctly.

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 100%, so the schema already documents all 9 parameters. The description adds almost no parameter-level meaning beyond the schema, but the baseline of 3 applies because the schema does the heavy lifting. The description's phrase 'input discarded' is vague and does not clarify which parameters are actually used.

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 'Murmur hash hex length, input discarded' is cryptic and does not state a clear verb or resource. It does not explain what the tool actually does or returns, and it does not distinguish it from siblings like search-query-len or memory-key-count. The name suggests a hash length, but the description leaves the purpose ambiguous.

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 given on when to use this tool versus alternatives. The description does not mention any context, conditions, or exclusions. With 29 sibling tools, the lack of usage guidance is a significant gap.

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