get_skill

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

Annotations are absent, so description carries the burden. It discloses 'Read-only disk read; errors if not found' and the lookup fallback order, giving agents a clear safety profile and error expectation.

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 organized into Behavior, Usage Guidelines, and Parameters sections in four concise sentences. Every sentence adds information and the main purpose is front-loaded.

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?

Despite no annotations and no output schema, the description covers what the tool returns (full markdown instructions and manifest), its read-only behavior, failure mode, and selection criteria. For a one-parameter get tool, nothing essential is missing, though a bit more detail about the return structure could help.

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 schema already documents the id parameter with case-insensitive lookup semantics at 100% coverage, but the description adds the precedence rule that exact skill ID is matched first, then falls back to case-insensitive name. This is meaningful extra meaning beyond 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?

Description uses specific verb 'Retrieve' with resource 'full markdown instructions and manifest for a skill by ID or name.' It distinguishes itself from route_skill by noting that route_skill is for searching by prompt intent, so an agent can tell them apart.

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?

Explicitly states when to use: when skill ID or name is already known (e.g. from route_skill or list_skills). It also states the alternative: 'Use route_skill to search by prompt intent,' providing clear selection logic.

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