add_skill

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

With no annotations, the full burden is on the description. It only implies creation, but fails to disclose any side effects, authorization needs, or limitations (e.g., duplicate handling, required project state).

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 single sentence is brief but lacks informative content. It is under-specified rather than concise, as it does not earn its place by adding non-trivial guidance.

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 6 parameters, no output schema, and no annotations, the description is severely incomplete. It fails to cover parameter usage, behavior, or return values, making it insufficient for correct tool invocation.

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%, yet the description adds no explanation for any of the 6 parameters. Parameters like 'scope', 'occasion', and cost fields remain completely opaque.

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 'Add a new skill to the database', which specifies the verb (Add), resource (skill), and location (database). This distinguishes it from tools like add_actor or add_item.

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?

No guidance on when to use this tool vs alternatives. Lacks context about prerequisites, constraints, or scenarios where adding a skill is appropriate.

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