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

Annotations already mark the tool as read-only, idempotent, and non-destructive, so the description does not need to restate safety. It adds useful behavioral specifics: the returned fields, the conditional verified-roster identity, and an illustrative slug format. Pagination or error behavior is not covered, but for a simple profile read this is acceptable.

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?

A single, front-loaded sentence with a clean colon-delimited list and one parenthetical example. Every element earns its place, with no filler or redundant restatement of the tool name.

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?

The definition is largely complete for a one-parameter read-only lookup: the schema documents the input, annotations cover safety, and the description lists the expected output fields. It could mention not-found or roster-exclusion behavior, but that is a minor gap given the tool's simplicity.

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 input schema has 100% documented coverage for the single slug parameter, including format, examples, and source URL. The description reuses the slug concept and gives a different example, but adds little beyond what the schema already provides, so the baseline 3 applies.

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 opens with a specific action ('Get a public company's Docket Nexus profile'), identifies the key input (slug), and enumerates the profile contents. This clearly distinguishes it from siblings like get_company_cases and search_cases, which target case lists rather than a single company profile.

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?

It establishes an unambiguous use case: retrieve a company-level profile by slug when you need company identity, linked case count, or top case types/courts. It does not explicitly name alternatives or state when not to use it, so it falls short of a 5, 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.