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

Annotations already provide readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds some context by naming the policy content, but it also states 'No inputs' despite an optional response_format parameter, which is imprecise and adds no useful behavioral detail beyond the annotations.

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 main sentence is front-loaded and states the tool's output efficiently. The appended 'No inputs' is short but unnecessary and slightly inaccurate, preventing a perfect score.

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 simple, read-only policy lookup with no required parameters, the description provides the essential content and the annotations carry safety semantics. It does not mention the optional response_format or define 'public machine data,' but these are minor given the schema and the tool's narrow scope.

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%, and the schema already documents response_format with its enum and default values. The description adds no parameter-level meaning, and its 'No inputs' statement is misleading because the schema allows an optional response_format, although the schema fully compensates.

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 uses a specific verb ('Returns') and names the exact resource: the platform's research-use-only boundary, prohibited uses, and allowed versus blocked public machine data. This clearly differentiates the tool from sibling lookups like defiance_catalog_search and defiance_evidence_lookup, which cover other content domains.

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 usage is implied by the named policy content, but the description gives no explicit guidance on when to use this tool versus alternatives, nor any 'use this when / not this when' framing. An agent must infer that policy-related questions are the intended use case.

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