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

Annotations already mark this as a non-read-only, non-idempotent, non-destructive, open-world write. The description adds important context: feedback is recorded but does not edit official data, a receipt means received for review rather than accepted or corrected, and submissions are associated with the verified account when signed in.

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 dense but front-loads the core purpose and call condition before moving into reporting expectations and receipt semantics. It is somewhat long for a single paragraph, but every sentence adds useful behavioral or usage 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?

For a complex 8-parameter submission tool with no output schema and partial schema coverage, the description gives substantial guidance on intent, privacy, evidence handling, account association and receipt meaning. It still leaves some secondary parameter semantics, especially issue_type and year/page_url/source_urls, to the schema.

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 only 38% schema description coverage, the description compensates well for the most important reporting parameters by explaining stand-alone content requirements, distinguishing user claims from verified facts, requiring a code or name for school/course reports, and warning not to guess a match. However, parameters such as year, page_url, source_urls and issue_type are not further clarified in 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 description states a specific verb and resource: submitting plain-text feedback to One U Education for internal review. It clearly distinguishes this from sibling lookup/search tools by stating it records feedback only and does not edit official data.

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?

It explicitly says to call only when the user wants to submit feedback, notes that an account is optional, and explains that signed-in submissions are linked to the verified account. It also clarifies that incomplete but useful leads are accepted, which prevents unnecessary hesitation.

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