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

With no annotations, the description carries the full burden of behavioral disclosure. The only possible behavioral hint is 'body discarded', but it is ambiguous—what body, under what circumstances, and with what effect? It doesn't disclose return values, side effects, permissions, or rate limits, which is a significant gap for a tool with no annotation support.

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, bordering on under-specification rather than efficient conciseness. The two fragments 'Yacc rule count' and 'body discarded' lack a clear relationship and don't form a coherent, useful statement. Like the 'Process' example, brevity here comes at the cost of essential meaning.

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, so the description must explain what the tool does, what it returns, and when to call it. It does none of these, making it impossible for an agent to know whether or how to invoke the tool. The description is completely inadequate for a tool with this parameter complexity.

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 all 9 parameters already have individual descriptions and the baseline is 3. The tool description adds no parameter-specific meaning and doesn't clarify which parameters are actually used, but it doesn't contradict the schema either. Thus the baseline score 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 'Yacc rule count, body discarded' is a noun phrase without an action verb, so it never states what the tool actually does (counts, validates, returns?). It names a domain (Yacc rules) but not a clear operation, and it doesn't distinguish itself from sibling tools like wiki-title-ok or search-query-len. This is vague rather than a tautology, but far below a clear purpose statement.

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 gives no indication of when to use this tool, what conditions favor it, or what alternatives exist. It provides neither explicit nor implicit usage guidance. Since it doesn't mislead about usage, it merits the 'no guidance' score rather than a 1.

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