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

With no annotations, the description carries the full burden and does meaningful work: it discloses that context blocks (Territory Solution JSON, GeoJSON, account/CSV tables) are stripped, forbids secrets/PII, and states an acknowledgement is returned. It stops short of saying where feedback goes, whether it's durable or anonymous, or how acknowledgement affects subsequent 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?

Five labelled fragments (When / Prerequisites / Next / Scenarios / content rules) are front-loaded and waste-free, with the triggering condition first. It is slightly telegraphic — 'Scenarios: GC-006' is opaque without external context.

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?

An output schema exists, so return values need not be explained, and the when/prerequisites/next flow is fully covered. The material gap is the 15-parameter surface: with 0% schema description coverage, the description should carry parameter meaning but does not, leaving a substantial completeness hole.

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% across 15 parameters, and the description never maps its guidance to specific fields — it does not distinguish user_goal from what_happened, nor explain category/severity/confidence enums, include_context, related_tool, or correlation_id. The content restrictions loosely imply what belongs in free-text fields, but most parameters get no explanation in either the schema or the description.

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 bracketed tag names the tier and function ('Quality Feedback'), and the 'When' clause makes the resource (feedback submission about workflow/tool quality) unambiguous. It doesn't name a contrasting sibling, but the purpose is immediately intelligible without opening the schema.

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?

Explicitly enumerates trigger conditions ('workflow blocked, partial, workaround required, confusing tool response, or missing capability/docs'), states 'Prerequisites: none', and specifies the follow-up ('Next: continue or end session after acknowledgement'). An agent knows exactly when to call this and what to do afterward.

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