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

Annotations already cover the safety profile with readOnlyHint=true, idempotentHint=true, and destructiveHint=false. The description adds value beyond that by disclosing that the tool is machine-readable, meant for pre-exchange evaluation, and enumerating the data-handling categories it covers. No contradiction with annotations; only the exact output format remains unspecified.

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 dense sentences with no filler; the first front-loads the topic and the coverage list, and the second adds the machine-readability trait. Every sentence earns its place and supports tool selection.

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 read-only, zero-parameter metadata tool with annotations covering safety, the description is nearly complete: it states the content, the trigger condition, and the consumption model. The only gap is that 'machine readable' does not specify the return format, and no output schema exists to fill that in.

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?

The tool takes zero parameters, so the schema trivially covers all inputs; the description appropriately focuses on output content rather than inputs. Per the rubric, a zero-parameter tool earns a baseline of 4. There is nothing more the description could meaningfully add about parameters.

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 clearly identifies the resource ('data use terms and consent wording') and enumerates its contents: who receives data, for what purpose, retention, revocation, and consent wording. It also distinguishes itself from siblings by tying to the request_agent_contact flow. However, it lacks an explicit retrieval verb, reading more as a statement of content than an action.

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?

The description gives an explicit trigger: 'the exact consent wording to present before request_agent_contact,' telling the agent when to consult this tool. It also frames the tool as a pre-exchange evaluation step ('so you can evaluate the exchange before making it'), implying a before/after ordering with request_agent_contact. It does not explicitly rule out alternative tools, but the context is clear.

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