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

No annotations are provided, so the description carries the burden. It states the action is a read, implying non-destructive behavior, but it does not disclose return format, error handling, or any side effects. The URI format hint is useful but overlaps with parameter semantics rather than behavioral transparency.

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 description is two sentences with zero fluff. The main purpose is front-loaded, and the arg example is compact and directly relevant. Every sentence earns its place.

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 simple read operation with one required parameter and no output schema, the description provides the URI format and a source for valid values. It does not explicitly state the return type, but the tool name 'read_skill' and the action 'read' make it adequately predictable. Minor omission of return details is acceptable given the low complexity.

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 input schema provides no description for the 'uri' parameter (0% coverage). The description compensates by giving a concrete example format (skill://<product>/<skill-name>/SKILL.md) and directing the agent to skills_list_tool for valid URIs, which adds significant meaning beyond the bare 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 states a specific action ('Read a product skill file') with a specific resource (a skill:// URI) and mechanism. It also references skills_list_tool for obtaining valid URIs, differentiating it from the listing sibling.

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 explicitly tells the agent where to get valid URIs (from skills_list_tool), implying a two-step pattern. It does not explicitly state when not to use this tool or list alternatives beyond that, but the context is clear enough for an agent to know it should be used after listing.

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