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

Annotations already provide readOnlyHint=true, openWorldHint=true, and destructiveHint=false. The description adds value by disclosing that full text is returned only when requested and is explicitly untrusted, plus the passthrough behavior ('their data comes back as it is'). These details go beyond the annotations without contradicting them.

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 opening sentence is clear and front-loaded, but the rest of the description is cluttered with server-level metadata, a listing URL, and an incomplete fragment ('Compare multiple plausible candidates for each —'). This extraneous content detracts from conciseness and structural quality.

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, the description should explain the return structure, but it only vaguely mentions 'descriptive catalog record' and 'full text'. It also fails to clarify how to specify id or what includeContent exactly changes. An agent cannot reliably call this tool based solely on the provided description.

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%, so the description must compensate for both parameters. It implies that 'id' identifies a local skill and that 'includeContent' controls whether full text is returned ('only when requested'). However, it does not specify the format of id or the exact output semantics, leaving meaningful gaps.

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 first sentence clearly states the tool retrieves a descriptive catalog record and, only when requested, the full text for a local skill. It names a specific action and resource, which distinguishes it from sibling tools that deal with files or search, though it does not explicitly name those alternatives. The purpose is somewhat obscured by unrelated server context later in the description.

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?

The description offers no explicit guidance on when to use this tool versus alternatives like search_skills or read_skill_file. The mention of 'Compare multiple plausible candidates for each' is incomplete and does not clarify selection criteria. Server-level notes about read-shaped tools are not usage guidance.

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