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

No annotations are provided, so the description carries the burden of behavioral disclosure. It states the output format (CSV text) and the included fields, which is useful. However, it does not disclose potential side effects (e.g., whether this is a read-only operation), performance implications (e.g., large data volume), or any authentication/authorization requirements. The description is adequate but lacks depth on behavioral traits beyond the basic output.

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 description is a single, concise sentence that front-loads the action ('Export the full controlled substance registration report') and specifies the format and content. Every word earns its place, with no redundancy or filler. It is appropriately sized for a parameterless tool.

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 the tool has no parameters and no output schema, the description is largely complete for an agent to understand what the tool does and what it returns. The only minor gap is the lack of explicit behavioral context (e.g., read-only nature, potential size), but for a simple export tool, the description covers the essential information. Sibling tools are listed, providing some context for differentiation.

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 has zero parameters, and the schema description coverage is 100% (empty properties). The description adds value by explaining what the report contains and the format, which is the only meaningful semantic information for a parameterless tool. Since there are no parameters to document, the baseline of 4 is appropriate, and the description effectively communicates the tool's output.

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 states the tool's function: exporting a full controlled substance registration report as CSV text. It specifies the resource (controlled substance registration report), the format (CSV text), and the included fields (prescriber, registration, expiry, status, reminder history). This distinguishes it from sibling tools like get_authority_summary or search_registrations, which are more focused on summaries or searching.

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 implies usage for obtaining a complete export of registration data, which is distinct from the sibling tools that provide summaries or filtered views. However, it does not explicitly state when to use this tool versus alternatives, such as 'use search_registrations for filtered queries' or 'use get_authority_summary for a summary.' The context is clear enough for an agent to infer the primary use case, but explicit exclusions or alternatives are missing.

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