disclosure_aup_check

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

No annotations provided, so description carries full burden. It reveals it only reports declared posture and lists statuses, but does not mention side effects, safety, idempotence, or error conditions. Adequate but could be more thorough.

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 sentences, straight to the point with no fluff. Front-loads purpose and includes key statuses and alternative.

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?

Given no output schema, annotations, or param descriptions, the description covers the output statuses and alternative tool but lacks input format and error handling details. Adequate for a simple check tool.

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?

Only one parameter 'document_json' with no schema descriptions (0% coverage). The parameter name hints at a JSON document but the description adds no further details on format, required fields, or structure.

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?

Clearly states the tool surfaces the disclosure's policy posture regarding AUP, lists the four possible status values, and distinguishes from sibling tool aup_check_compliance.

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 says it reports declared posture only and directs to aup_check_compliance for the actual three-way join, but does not mention when not to use or other alternatives among the many siblings.

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