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

Annotations already provide readOnly, idempotent, and non-destructive hints, so the safety profile is covered. The description adds 'public metadata' and 'Metadata only; no document text,' which is valuable context about the tool's return type and limitations. It doesn't contradict annotations and adds meaningful behavioral detail beyond what annotations encode.

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 concise sentences: the first states the action and the exact metadata fields returned; the second explicitly excludes document text. Every word contributes, and the core 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 simple single-id metadata lookup with no output schema, the description is complete. It lists the returned fields, clarifies the parameter source, and sets the expectation of 'metadata only,' so an agent can invoke the tool without needing additional context.

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?

With 0% schema description coverage, the description must compensate, and it does for the only parameter: 'by its Docket Nexus document id' clarifies what document_id means and its domain. It doesn't explain how to obtain that id, but for a single well-named integer parameter, this is sufficient semantic support.

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 ('Get'), a specific resource ('public metadata for a docket document'), and an explicit field list (entry, date, description, page count, availability, parent case). It also adds 'Metadata only; no document text,' which clearly distinguishes this tool from any document-text retrieval and from sibling case/company tools.

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 clearly implies when to use this tool: when you have a Docket Nexus document id and need that document's metadata. It doesn't explicitly name alternatives or exclusions (e.g., 'use get_case_docket for the full docket'), but the focus on a single document by id is enough for an agent to select it correctly in most cases.

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