aura_get_skill

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

No annotations are provided, so the description carries the full disclosure burden. It notes the returned fields (source_url, page URL) and hints at "free" content, but says nothing about auth requirements, error behavior, or whether the skill must be installed first.

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?

Extremely short but under-specified rather than concise: two sentence fragments that read like field notes. The most useful information (returned fields) is present but no sentence fully earns its place by being self-contained.

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 one-parameter getter with no output schema and no annotations, the description does at least list return fields, but it leaves the identifier semantics and the relationship to search/install siblings unexplained, so an agent cannot confidently place it in a workflow.

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?

One parameter at 0% schema description coverage. The trailing fragment "Skill id." merely restates the schema property name 'id' and adds no format, source, or identifier-scheme detail to help the agent supply a valid value.

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 names the resource ("Full free agent-skill content (SKILL.md body)") and implies a fetch by id, which an agent can distinguish from aura_search_skills. However, it uses no explicit verb and reads as a fragment list rather than a statement of what the tool does.

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?

There is no when-to-use guidance and no mention of the obvious alternative, aura_search_skills, or aura_install_skill. The agent must infer that this is the retrieval step after a search.

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