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

Annotations already cover readOnly/idempotent/destructive/openWorld, and the description adds meaningful context beyond them: transient non-retention of inputs, a directive to use synthetic data only, server-vs-browser delegation behavior, and production of an AP2 artifact with execution_hash. These are real behavioral disclosures, though much reads as platform boilerplate rather than tool-specific behavior.

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?

Front-loaded with the name but then spends most of its length on compute-binding mechanics, a URL, and an FV-status hash path whose relevance to invocation is marginal. Dense and not fully waste-free.

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?

Output schema exists, so return values need not be explained, and zero params are required. But for a compliance-mapping tool the description never explains what got mapped or what policy_parameters should contain ('see the tool's manifest'), leaving the substantive semantics undocumented.

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 100%, so the schema already documents compute, parent_hashes, parent_tool_ids and policy_parameters. The description's compute-mode prose largely duplicates the schema's enum description and adds nothing on chaining or policy_parameters fields. Baseline 3 applies.

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 opens by restating the tool name and labeling it a generic 'OpenChainGraph compute node (compliance_mandate)' rather than stating the mapping action. It never says what NIST AI RMF functions it maps or to what. An agent learns more about the platform's compute routing than about the tool's actual purpose.

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 names downstream consumers ('Output feeds: art-175..., art-314...') but gives no when-to-use guidance versus siblings like assess_ai_act_conformity or check_gpai_code_conformance, no prerequisites, and no exclusions. Downstream routing is not the same as invocation guidance.

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