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

Annotations already declare readOnly, idempotent and non-destructive. The description adds real context: the read is optional and version_id guarantees no silent substitution of current content. It says nothing about what the call returns or how outcome pagination behaves, which matters because there is no output schema.

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 zero filler; the optionality caveat is front-loaded so the agent learns the fallback status before anything else.

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 4-param read tool with no output schema, the description should say at least roughly what comes back (skill content plus a paginated outcome list). It covers scope and version fidelity but omits return shape and pagination 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 coverage is 50%: version_id and outcome_cursor are documented in-schema, skill_id and outcome_limit are not. The description reinforces version_id semantics ('exact immutable version') but leaves outcome_limit, cursor usage and the skill_id format entirely to 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 gives a specific verb and resource ('direct read of a reusable skill or exact immutable version') and clarifies that matched solutions arrive through problem responses, which separates this from read_problem. Siblings are not named explicitly, so the differentiation is indirect rather than crisp.

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?

'Optional direct read' plus 'matched solutions are already included in problem responses' implies this is a fallback when the skill isn't already surfaced. No explicit when-to-use trigger or named alternative (e.g. describe_problem, read_problem) is given, so the agent must infer the routing rule.

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