yaaif_skill_get

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

There are no annotations, so the description carries the full behavioral burden. It only hints at an implementation detail with 'via catalog list ?ids=' and does not disclose whether this is read-only, what happens when the ID is not found, or what the response shape is. This is minimal behavioral information.

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 with no filler. It states the core operation first and keeps the implementation hint in a parenthetical, making it easy to scan.

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 one-parameter getter, the core invocation path is reasonably clear: supply a skill_id and get one skill. However, without an output schema or any guidance on return format, errors, or when to use this versus listing skills, an agent still faces meaningful 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 0%, and the description only says 'by id'. It does not clarify the expected format of skill_id, whether multiple IDs are accepted despite the singular parameter name, or what 'via catalog list ?ids=' means for parameter usage. The description does not meaningfully compensate for the schema's lack of detail.

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 states a specific action and resource: 'Get one skill by id'. The word 'one' clearly distinguishes this from the sibling skill-list tools, so an agent can immediately tell what the tool is for.

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 the tool is for retrieving a single skill when you already have its ID, but it does not explicitly say when to prefer this over yaaif_skill_list or other skill-related tools. No alternatives or exclusion criteria are provided.

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