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

With no annotations, the description carries the behavioral disclosure burden. It discloses the output envelope (grade, cite, canonical), the format-selection behavior via extension suffix, and the fact that operand params are passed through the address query string. The verb 'Fetch' implies read-only; a few more side-effect or error details would elevate it.

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 sentences deliver purpose, output shape, format switching, and query-parameter behavior with no filler. Some jargon ('typed envelope', 'drills') is dense, but the information density is high and the key purpose is 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?

For a single-parameter fetch tool with no annotations and no output schema, the description covers the essential details: what to fetch, what the envelope contains, how to select serialization, and how to pass operands. A concrete address example and a clearer definition of 'register' would make it fully complete, but nothing critical is missing.

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 coverage is 0%, so the description must define the 'address' parameter. It does: an address points to a record/work/party/receipt page, can take a .json/.md/.html suffix, and accepts query parameters like facet, group_by, sum, and limit. It doesn't provide a concrete address example or enumerate valid facet names, but it gives meaningful construction semantics beyond the bare string schema.

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 names a specific action ('Fetch') and resource ('one address of the publication — a record, work, party or receipt page'), and enumerates the returned envelope fields (grade, cite, canonical). It clearly states what drill does, though it does not explicitly contrast with the sibling 'search' tool beyond the singular-address wording.

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 provides clear operational guidance on how to use drill — append .json/.md/.html to select a register, or use a bare address for agent-markdown — and notes that query params ride the address. However, it never states when to choose drill over search or lists exclusions, so the usage boundary is only implied.

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