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

No annotations are provided, so the description carries the full behavioral burden. It describes the provenance fields returned and implies a read operation via 'Read this', but does not explicitly state there are no side effects, prerequisites, or failure modes. Adequate for a simple lookup but not fully transparent.

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 short sentences with no filler. The list of returned provenance fields is front-loaded, followed by the usage directive, making it easy for an agent to parse quickly.

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 0-parameter provenance tool with no output schema, the description lists the key return fields and the intended use. It does not specify the exact return format, but that is a minor gap for this simple metadata lookup.

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 has no properties, so the description correctly says nothing about parameters. The baseline for a 0-param tool is 4; there is nothing more the description needs to add.

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 the resource (the Enpso dataset) and the exact information returned (source, computed date, licence, citation), with a clear action: 'Read this to attribute a figure correctly.' This distinguishes it from sibling tools that handle columns, searching, stats, or row access.

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 provides a concrete use case: use this to attribute a figure correctly. It does not explicitly name alternatives or when not to use it, but the title and content make the context clear relative to the other dataset tools.

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