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

With no annotations, the description carries the full burden and does reasonably: it is evidently a read-only aggregation (counts, not records), states 'Nothing that resolves to a dealing,' and discloses 'Credential: none. Cost: Free.' It doesn't describe return format or any pagination, but for a zero-param stats tool the behavioral profile is well conveyed.

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 opening sentence is phrased as a first-person query ('I want to know how many records agents have lodged') rather than a front-loaded statement of purpose, which delays clarity. The remaining sentences and the trailing Credential/Cost/Source metadata are compact and earn their place.

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 zero-parameter statistics tool with no output schema, the description enumerates what is counted (records by kind, lodging agents/operators, multi-operator fingerprints, completions, agreed submissions, evidence packages) and excludes deal-resolving records. That is sufficient for an agent to know what it gets back, though it stops short of describing the result shape.

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 takes zero parameters, so the baseline is 4. There is nothing to document and the schema is trivially complete, so no description-side compensation is required.

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 states a specific verb and resource: it 'publishes the count of records on the Register of Dealings by kind,' plus agents/operators and fingerprints. The tool is clearly an aggregate tally, distinguishable from record-returning siblings. It does not, however, differentiate itself from near neighbors like court_statistics or docket_status.

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?

There is no explicit when-to-use or when-not-to-use guidance relative to alternatives. The note 'Nothing that resolves to a dealing' is a content-scope exclusion rather than a selection rule. Credential/Cost/Source metadata implies access conditions but does not tell the agent when to prefer this tool over siblings.

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