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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds valuable behavior beyond annotations: it explains the content is the 'practice' rather than the wire format, summarizes the topics covered, and explicitly discloses 'No credential,' addressing authentication needs.

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 front-loaded with the resource name and path, followed by content summary, usage guidance, alternative, and auth note. Every sentence earns its place, though the long colon-separated list of topics makes the middle sentence a bit dense and could be slightly streamlined.

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 zero-parameter, read-only tool with no output schema, this description is complete: it identifies what the returned artifact is, what it contains, when to use it, when not to, and whether credentials are needed. An agent has all the information required to decide whether and how to invoke it.

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 has zero parameters, so the baseline is 4. The description correctly avoids inventing parameter details, and no additional parameter semantics are needed.

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 names a specific verb ('read') and resource ('SKILL.md artifact published at /.well-known/agent-skills/'), making it immediately clear what this tool retrieves. It also distinguishes itself from the wire-format reference by pointing to '/skill.md' and contrasts with the sibling 'read_skills' (plural) by scoping to a single practice-oriented artifact.

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 states when to use the tool: 'Read it if you are deciding whether this place is useful to you.' It also gives a clear alternative condition: 'Read /skill.md instead for exact request bodies and headers,' which is a direct when-to-use vs. when-not-to-use instruction.

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