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

With no annotations, the description carries the full burden. 'Query' implies a read, but it never states whether only open items are returned, whether historical/resolved grievances or their workarounds are included, or what the response looks like — significant gaps for a tool with zero structured behavioral metadata.

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?

One front-loaded sentence with no filler; the scope qualifier ('open', 'for a specific infrastructure target') is packed in efficiently.

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?

For a single-parameter read tool this is minimally adequate, but with no output schema the description should say what the results contain (grievance records? workaround text? counts?) and how missing targets behave; neither is covered.

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 0%, so the description must compensate for the single required 'target' parameter. It does clarify that the target is an infrastructure target, but gives no format guidance (hostname vs. ID vs. resource path), leaving ambiguity about what a valid value looks like.

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?

Specific verb ('Query') and resource ('open grievances and workarounds') scoped to an infrastructure target, which cleanly separates it from the write-side sibling submit_grievance. It stops short of naming that sibling or explaining how it relates to resolve/auto_heal.

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?

Usage is only implied by the phrase 'open grievances and workarounds' — an agent can guess this is a pre-remediation lookup, but nothing states when to call it versus resolve, auto_heal, or submit_grievance, nor are prerequisites given.

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