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

Annotations already cover safety traits (readOnly, openWorld, idempotent, non-destructive), but the description adds no behavioral context. It doesn't state whether this is a lookup, whether it returns one or multiple entries, or any limitations. The description is purely topical and redundant with the title.

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 concise (4 words) but under-specified. It is a fragment that omits the core operation and any useful detail. Brevity without substance does not justify a higher score.

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?

Even with an output schema present, the description is too sparse to provide adequate context. It doesn't explain what a working group is, how acronyms are resolved, or when to use this tool. The schema examples hint at IETF, but the description itself leaves the agent guessing.

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?

With schema description coverage at 0%, the description needed to explain the 'acronym' parameter. However, it only says 'by acronym,' which is already evident from the parameter name. It does not clarify the domain (e.g., IETF working groups), expected format, or any constraints.

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 'Working group by acronym' is a noun phrase that indicates the tool concerns working groups and uses an acronym, but lacks an explicit verb (e.g., lookup, retrieve). It vaguely suggests a direct lookup but does not clearly distinguish from sibling tools like 'wgs_search'.

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 tool versus alternatives. The description does not mention any context, prerequisites, exclusions, or scenarios where another tool would be more appropriate.

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