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

Annotations already cover read-only, idempotent, and non-destructive behavior. The description adds useful conditional nuance by noting verified identity appears only 'when on the verified roster' and clarifies the aggregate nature of the response, such as 'number of linked cases' and 'top case types and courts.'

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 front-loaded sentence with no filler: it states the verb, resource, key constraint, example, and output fields in order. The enumeration is dense, but every item earns its place and there is nothing irrelevant.

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 one-parameter getter with no output schema, the description covers the input format and the main return contents, including the verification conditional. It does not describe error or unknown-slug behavior, but that is a minor gap for such a simple read-only tool.

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% and the single parameter is documented only by its title, so the description carries the burden. It explains that the slug identifies a company and gives a concrete example ('acme-widgets-inc'), making the expected value actionable despite the sparse 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 verb ('Get'), a distinct resource ('Docket Nexus profile'), an addressing mode ('by slug'), and enumerates returned fields, so an agent can tell this from get_case and search_cases. It does not explicitly contrast with get_company_cases, but the profile-vs-cases distinction is clear enough from the resource 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 implies when to use it: when the agent has a company slug and needs an aggregate profile rather than case-level records. It gives no explicit when-not-to-use or alternative routing, such as pointing to get_company_cases for the full case list, so usage context must be inferred.

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