disclosure_validate

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

Discloses that it enforces conditional validation rules, which adds value beyond schema. However, with no annotations, it lacks details on error reporting, side effects (read-only implied), and response format.

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 concise sentences: first defines purpose, second details conditional rules. No extraneous content, front-loaded.

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?

Covers validation logic well but omits important context: no output schema means result format is unknown, no mention of synchronous/asynchronous behavior, and no prerequisites stated.

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 has one parameter with 0% description coverage. The description adds that it is a 'Student AI Disclosure JSON document' but fails to specify expected format, encoding, or constraints, which is insufficient for correct usage.

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 validates a Student AI Disclosure JSON document against a specific schema (v0.1). This distinguishes it from sibling tools that validate other document types (e.g., agent_card_validate, tutor_card_validate).

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?

Describes the conditional rules enforced, which guides when to use this tool (disclosures with those rules). No explicit when-not or alternatives, but the specific context makes usage clear.

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