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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the closing 'Read only' is redundant. However, the description adds genuinely non-obvious behavior the annotations don't cover: it 'costs one LLM call,' is 'rate limited,' and 'cites the matching articles.' This is real operational context that changes how an agent should batch or throttle calls.

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?

Two tightly packed sentences with zero filler. The core purpose is front-loaded, followed by cost/limit constraints and then the read-only note. Every clause earns 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?

With no output schema, the description usefully signals the return shape by stating it 'cites the matching articles.' Annotations cover the safety profile, and the description adds cost, rate-limit, and phrasing constraints. Complete enough for a one-parameter read tool, though it could say more about result formatting or empty-result behavior.

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 single parameter has 0% schema description coverage — the schema only supplies minLength/maxLength bounds. The description partially compensates by indicating the question should be a 'how-does-Blawgy-work' query kept 'specific,' but it adds no format, scope, or content-shape detail. Baseline of 3 is appropriate given the schema does not carry the meaning.

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 a specific verb and resource: it 'answers a how-does-Blawgy-work question from the public help docs and cites the matching articles.' That clearly separates it from the closest sibling, file_support_request (which files a ticket rather than answering). It stops short of naming any alternative explicitly, so it is clear but not sibling-differentiating in the strongest sense.

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?

'Keep questions specific' is the only usage guidance, and it is about phrasing rather than when-to-use. There is no statement of when to prefer this over file_support_request or other tools, nor any exclusion criteria. Usage is implied by the phrase 'how-does-Blawgy-work question'.

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