skills_create

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

Annotations already indicate this is a read/write operation (readOnlyHint=false). Description adds that body is a prompt template with placeholders, but this is largely redundant with the schema. No additional behavioral traits disclosed beyond annotations.

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?

Single sentence that is concise and front-loaded with the main action. No unnecessary words or redundancy.

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?

Lacks description of return values or side effects, and does not cover details like parameter requirements or behavior when optional fields like save_to_space_id are used. For a creation tool with 8 parameters and no output schema, more context would be helpful.

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?

Description adds slight value by clarifying that the body uses {{variable}} placeholders for input_params at runtime, which is more explicit than the schema's description. However, many parameters (name, project_id) remain undefined, and overall schema coverage is 63%.

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?

Description clearly states 'Create a new Skill in a project' with specific verb and resource. It also explains the nature of the body field as a markdown template, distinguishing it from sibling tools like skills_update or skills_get.

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 explicit guidance on when to use this tool versus alternatives. Does not mention scenarios like creating a new skill vs updating, nor any prerequisites or context for invocation.

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