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

Annotations already declare readOnlyHint, idempotentHint, and closed-world behavior, so safety is covered. The description adds the scope note that results come from the same default consumer MCP connection, but says nothing about the limit/pagination behavior implied by the schema, so it adds only modest value.

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?

A single front-loaded sentence with no filler; the resource enumeration is dense but earns its place. It is appropriately sized, though slightly under-informative rather than over-wordy.

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?

With no output schema and completely undocumented parameters, the description should explain what is returned (topics vs skills vs artifacts) and how limit/category shape the result. It leaves the agent unable to predict result shape or filtering behavior.

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 description coverage is 0% and neither parameter (limit, category) is explained in the description. The phrase 'runtime skills' loosely hints at the 'skills' enum value, but there is no mention of the category filter or the 1-25 limit, so the description fails to compensate for the coverage gap.

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?

States a clear verb (List) and a concrete resource set (documentation topics, runtime skills, machine-readable artifacts), which is more specific than the title. It does not explicitly distinguish itself from siblings docs_search and docs_get_resource, so it falls short of 5.

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 when-to-use or when-not-to-use guidance, and no alternative tool is named despite docs_search and docs_get_resource sitting in the same family. The only contextual clue is 'same default consumer MCP connection', which hints at scope but does not tell the agent when to pick this over search.

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