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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is fully covered structurally. The description adds only that the return is the full markdown playbook, plus an output schema that likely documents the shape. No mention of size, auth, or truncation behavior beyond what annotations and the output schema already give.

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 primary action is stated first and the routing hint second. Every clause carries information.

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?

Because an output schema exists, the description needn't explain return values, and the read-vs-execute distinction is handled. The real gap is the sole required parameter with no schema documentation and no description of where skillId is obtained, which is exactly what an agent needs before calling.

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 single required parameter skillId has 0% schema description coverage, so the description is the only place semantics could be supplied — and it says nothing about it. It never explains that the ID comes from a discovery call such as list_skills or what format it takes, leaving the agent to guess where the value originates.

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?

Specific verb+resource: 'Load full skill playbook markdown' tells the agent exactly what comes back (markdown playbook text). It also names a sibling, run_playbook, that an agent might otherwise confuse it with. It does not, however, distinguish itself from list_skills, which is the natural discovery counterpart.

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?

'Prefer run_playbook to execute in one step' gives an explicit alternative and the condition (execution) that selects it, which implicitly frames load_skill as the inspection path. It stops short of explicitly stating when to read versus execute, so the agent must infer the read-only-inspection use case.

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