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

With only readOnlyHint declared, the description adds real value by enumerating the return shape (skill ID, target property, description, required arguments) — especially important since there is no output schema. It also explains why the data matters (team-authored methodology and output format). It does not mention pagination or scoping limits, which keeps it short of a 5.

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, both front-loaded with the highest-value information: the first defines the tool and its output, the second gives the routing rule. No filler or repetition of the title.

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 parameterless read tool with no output schema, the description covers purpose, domain terminology, returned fields, and downstream routing to get-skill. An agent has everything it needs to decide to call it and to use the result correctly.

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 there is nothing for the description to disambiguate; baseline is 4. The description's mention of 'accessible properties' usefully clarifies the implicit scope of the listing even though no input exists.

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 specific verb and resource ('List the AIdata skills') and immediately defines the domain term with a parenthetical gloss ('authored report/analysis playbooks'), so an agent knows exactly what a skill is. It also distinguishes itself from the sibling get-skill by framing itself as the discovery step and get-skill as the execution step.

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?

Gives a clear usage context: when a user asks for a report or audit that matches a skill, prefer running the skill via get-skill over improvising. It names the alternative tool and the condition that selects it, but the guidance is framed around using get-skill rather than explicitly stating when to call list-skills (i.e., to discover which skills exist first).

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