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

With no annotations provided, the description carries full burden for behavioral disclosure. It states a read operation ('Get'), implying non-destructive behavior, but doesn't cover authentication needs (api_key parameter), rate limits, error conditions, or response format. The description adds minimal behavioral context beyond the basic action.

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 a single, efficient sentence that directly states the tool's purpose without unnecessary words. It's appropriately sized for a simple retrieval tool and front-loads the essential 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?

For a retrieval tool with no annotations and no output schema, the description is insufficient. It doesn't explain what 'full prompt pattern content' includes, the response format, or error handling. Given the lack of structured metadata, the description should provide more complete operational context.

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 100%, with both parameters well-documented in the schema. The description adds no additional parameter semantics beyond what the schema already provides (slug examples, api_key purpose). This meets the baseline score when schema coverage is high.

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 clearly states the action ('Get') and the resource ('full prompt pattern content'), specifying retrieval by slug. It distinguishes from sibling tools like list_prompts (which lists rather than retrieves content) and get_template/get_skill (different resource types). However, it doesn't explicitly differentiate from all siblings in the description text itself.

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 provides no guidance on when to use this tool versus alternatives. It doesn't mention when to choose get_prompt over list_prompts (for full content vs listing), or how it relates to get_template/get_skill for different resource types. No usage context or prerequisites are provided.

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

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

No annotations are provided, so the description carries the full burden. It discloses the tool fetches 'full SKILL.md content' and requires a slug, but doesn't mention authentication needs (api_key parameter), error handling, rate limits, or response format. While it adds some context about the content type, key behavioral aspects remain undocumented.

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 sentences with zero waste: the first states the purpose and resource, the second provides essential usage guidance. It's front-loaded with the core function and efficiently includes only necessary context about sibling tools.

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 2 parameters and no output schema, the description covers purpose and sibling differentiation well. However, without annotations or output schema, it lacks details on authentication (api_key), error cases, or return format, leaving gaps in behavioral context despite the straightforward function.

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 100%, so the schema already documents both parameters (slug and api_key) with descriptions. The description adds no additional parameter semantics beyond implying slug usage, which the schema already covers. Baseline 3 is appropriate when the schema does the heavy lifting.

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 clearly states the action ('Get the full SKILL.md content') and resource ('for a specific Claude Code skill by slug'), distinguishing it from siblings like list_skills (which discovers slugs) and other get_/list_ tools for different resources. It specifies the exact content format (SKILL.md) and mechanism (slug-based lookup).

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?

It explicitly states when to use this tool ('by slug') and provides a clear alternative for discovering slugs ('Use list_skills to discover available slugs'), directly addressing sibling differentiation. This gives complete guidance on the workflow: first use list_skills, then use get_skill with a slug from that list.

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

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

With no annotations provided, the description carries full burden for behavioral disclosure. It states the tool retrieves content but doesn't describe what 'full CLAUDE.md template content' entails (e.g., format, structure, size), whether it requires authentication (implied by 'api_key' parameter but not stated), or any rate limits or error conditions. This leaves significant gaps for an agent to understand the tool's behavior beyond basic retrieval.

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 a single, efficient sentence that front-loads the core purpose ('Get the full CLAUDE.md template content') and specifies the key constraint ('for a specific project type by slug'). There is no wasted verbiage, and every word contributes to understanding the tool's function.

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?

Given the tool's moderate complexity (2 parameters, no output schema, no annotations), the description is adequate but incomplete. It covers the basic retrieval action and target resource, but lacks details on authentication needs (implied by 'api_key' but not explained), output format, or error handling. Without annotations or output schema, the agent must infer these aspects, making the description minimally viable but with clear gaps.

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 100%, with both parameters ('slug' and 'api_key') well-documented in the schema. The description adds minimal value beyond this, mentioning 'by slug' which aligns with the schema but not providing additional context like example slugs or how 'api_key' relates to authentication. Baseline score of 3 is appropriate as the schema does the heavy lifting.

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 clearly states the action ('Get') and resource ('full CLAUDE.md template content for a specific project type by slug'), making the purpose immediately understandable. It distinguishes from siblings like 'list_templates' by specifying retrieval of full content for a specific template rather than listing available templates. However, it doesn't explicitly contrast with 'get_prompt' or 'get_skill', which might have similar retrieval patterns.

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 implies usage context by specifying 'for a specific project type by slug,' suggesting this tool should be used when you need the complete template content for a known template identifier. However, it provides no explicit guidance on when to use this versus alternatives like 'list_templates' (for browsing) or other 'get_' tools, nor does it mention prerequisites or exclusions.

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

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

No annotations are provided, so the description carries full burden. It describes the tool's behavior as listing patterns with specific fields, but doesn't disclose operational traits like pagination, rate limits, authentication needs (though the schema shows an optional api_key), or error handling. The description adds basic context but lacks deeper behavioral details.

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 extremely concise with two sentences that are front-loaded and waste-free. The first sentence states the purpose and output fields, while the second provides usage guidance, with every word earning its place. No redundant or verbose language is present.

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?

Given the tool's low complexity (one optional parameter, no output schema, no annotations), the description is reasonably complete for a listing operation. It covers purpose, output fields, and sibling differentiation, but lacks details on behavioral aspects like response format or error cases, which would be helpful despite the simple context.

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 100%, so the schema already documents the single parameter (api_key). The description doesn't add any parameter-specific information beyond what the schema provides, such as explaining when or why the api_key is needed. Baseline 3 is appropriate when the schema handles parameter documentation adequately.

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 clearly states the specific action ('List all available prompt patterns') and resource ('prompt patterns'), while distinguishing it from sibling tools by mentioning that 'get_prompt' should be used to fetch full content. It provides exact fields returned (slug, title, category, tags), making the purpose highly specific and differentiated.

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 this tool ('List all available prompt patterns') versus alternatives ('Use get_prompt to fetch the full prompt content'), providing clear guidance on tool selection. It distinguishes this listing tool from the detailed retrieval sibling, though it doesn't mention other siblings like list_skills or list_templates.

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

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It clearly describes what the tool does (lists skills with specific fields) and mentions the relationship with get_skill. However, it doesn't address important behavioral aspects like whether this requires authentication (though the schema shows an optional api_key parameter), rate limits, pagination, or error conditions. The description adds value but leaves gaps in 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 perfectly concise with two sentences that each serve distinct purposes: the first explains what the tool does and what information it returns, the second provides explicit usage guidance by contrasting with a sibling tool. There is zero wasted text, and the information is front-loaded with the core functionality.

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?

Given the tool's moderate complexity (listing operation with one optional parameter), no annotations, and no output schema, the description does a good job of explaining the tool's purpose, output format, and relationship to other tools. However, it doesn't address authentication requirements (implied by the api_key parameter but not explained), error handling, or what happens when no skills are available. For a tool with no annotations or output schema, it's mostly complete but has minor gaps.

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 description coverage is 100% with one parameter (api_key) documented in the schema. The description doesn't mention parameters at all, which is appropriate since the schema fully documents the single optional parameter. With zero parameters mentioned in the description and high schema coverage, the baseline would be 3, but the description effectively focuses on the tool's purpose rather than repeating schema information, earning a slightly higher score.

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 clearly states the specific action ('List all available Claude Code skills') and the resource ('skills'), including what information is returned ('slug, title, category, and description'). It also distinguishes from the sibling 'get_skill' by mentioning that tool fetches full content for a specific skill, while this one lists all skills with summary information.

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 provides explicit guidance on when to use this tool versus alternatives: 'Use list_skills to see all available skills with summary information' (implied) and 'Use get_skill to fetch the full SKILL.md content for a specific skill.' This clearly differentiates between browsing all skills and getting detailed content for one skill.

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

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

No annotations are provided, so the description carries the full burden. It describes the tool as a list operation (implying read-only behavior) and mentions the output fields, but doesn't disclose behavioral traits like pagination, rate limits, authentication needs (though the schema shows an optional api_key), or error handling. The description adds some context but lacks depth for 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, front-loaded with the core purpose and followed by a usage guideline. Every sentence earns its place by providing essential information without waste. It's appropriately sized for a simple list tool.

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?

Given the tool's low complexity (1 optional parameter, no output schema), the description is somewhat complete but has gaps. It explains what the tool does and references an alternative, but lacks details on authentication (implied by api_key but not explained), output format beyond field names, or error cases. Without annotations or output schema, more context would be helpful.

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 100%, so the schema already documents the single parameter (api_key). The description doesn't add any parameter-specific information beyond what the schema provides. With high schema coverage, the baseline score is 3, as the description doesn't compensate with additional semantics.

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 clearly states the tool's purpose: 'List all available CLAUDE.md templates with slug, title, and category.' It specifies the verb ('List'), resource ('CLAUDE.md templates'), and output fields. However, it doesn't explicitly differentiate from sibling tools like 'list_prompts' or 'list_skills' beyond mentioning a different resource type.

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 provides clear context: 'Use get_template to fetch the full template content.' This explicitly names an alternative tool for a related action (fetching content vs. listing metadata). However, it doesn't specify when to use this tool versus other list tools like 'list_prompts' or 'list_skills'.

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