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

The readOnlyHint annotation already covers the main behavioral trait, so the description does not need to restate it. The description offers no additional behavioral detail, but there is no contradiction with the annotation.

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 short and front-loaded with the main verb and object, but it includes unclear and extraneous content such as 'each one body's collection', the parenthetical examples, and the stray 'norm.', which reduce clarity and polish.

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 simple listing tool with no output schema, the description gives the basic idea but leaves important context unaddressed: it does not clarify what the returned catalogues look like, how pagination works, what the language parameter affects, or the relationship to publishers/contributors.

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 only 33% (only 'limit' is described), and the description does not explain 'lang' or 'page' beyond their names. Since lang/page meaning is not fully obvious and no compensation is provided, the description adds little value over the 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 uses the specific verb 'List' with the resource 'catalogues' and adds context that they 'feed I14Y', which distinguishes it from closely related i14y list tools such as list_datasets and list_public_services. However, the phrase 'each one body's collection' and the parenthetical examples are slightly fuzzy.

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 gives a vague use case ('use to see who contributes') but provides no explicit guidance on when to use this tool versus related list/search tools, and no pagination or parameter usage guidance. The trailing 'norm.' appears to be leftover text and adds no usable direction.

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