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

With no annotations provided, the description carries the full disclosure burden. It does reveal the returned information categories, implying a read-only metadata operation. It does not state side-effect safety or response format, but for a zero-parameter metadata accessor that omission is minor.

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 with the content list front-loaded and a user-oriented usage note at the end. No filler or repeated schema information.

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 description gives the tool's entire purpose, content list, and a concrete invocation trigger, which is adequate for a parameterless provenance lookup. Without an output schema it could have included more detail on the exact structure, but the listed fields are sufficient for an agent to know when and why to call it.

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 has zero parameters, and the schema is trivially 100% covered. There is nothing for the description to add about argument semantics, so the baseline score of 4 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 enumerates the exact content returned (source, computed date, licence, citation) for the named BreakerDesk dataset, which clearly distinguishes it from sibling tools that handle columns, rows, search, stats, and comparisons. It lacks an explicit action verb, but the noun-phrase framing is unambiguous and resource-specific.

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 statement 'Read this to attribute a figure correctly' gives a concrete when-to-use trigger tied to citation and attribution needs. It does not explicitly name alternatives, but no sibling tool serves the same provenance purpose, so the guidance is sufficient.

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