strata_skill

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

No annotations are provided, so the description must carry the behavioral burden. It discloses that the tool is a getter returning 'full SKILL.md content' for a named skill. It does not mention behavior on invalid or missing skill names, case sensitivity, or that it is read-only (though 'Get' implies this).

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, front-loaded sentence that uses no filler. Every word contributes to the tool's purpose and scope.

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?

With one required parameter and an output schema present, the description is largely complete. It names what the tool returns and scopes it to a specific skill. The only notable gap is no guidance on what happens if the skill is not found or how to obtain a valid name, but these are minor for such a simple getter.

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 0%, so the description must clarify the 'name' parameter. It does tie the parameter to 'a specific skill', which gives some meaning beyond the schema's bare string type. It does not explain how to identify valid names or provide examples, but with only one parameter this may be sufficient.

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 uses a specific verb ('Get') and resource ('full SKILL.md content') scoped to 'a specific skill'. This clearly distinguishes it from siblings like strata_list_skills, which lists skills, and other strata_* tools about queries or dependencies.

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: call this when you have a specific skill name and want its full content. However, it does not explicitly state when to use this over siblings (e.g., use strata_list_skills to discover names first) or any exclusions.

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