skills_get_asset

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

Describes the two-phase pattern and that it returns content for templates. No annotations provided, so description carries burden; it adds enough behavioral context for a read operation. Could mention idempotency but not needed.

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?

Three short paragraphs, structured with numbered steps, no wasted words. Front-loaded with purpose and clear instructions.

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?

Complete for a 2-parameter tool with output schema. Covers when to call, how to use (two-phase), and what to do with content. No gaps given the simplicity.

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 coverage is 0% but description explains filename default and 'list' behavior, and that skill_id is required. Adds meaning beyond schema for filename, though skill_id is self-explanatory.

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 it fetches a template or static resource bundled with a skill, listing examples like markdown templates, config starters, and data files. It distinguishes from sibling tools like skills_get_body and skills_get_reference by focusing on assets.

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?

Explicit two-phase usage: first call with filename='list' to see manifest, then fetch specific file. Also states 'Only call when skill instructions reference a specific asset file,' providing clear context. However, no explicit comparison with sibling tools.

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