paperclip_sync_agent_skills

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

The description explains the tool modifies agent skills (adding/removing), which aligns with the destructiveHint annotation. It also details return values (added[], removed[], current[]) and error codes, adding behavioral context 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?

The description is efficiently structured with Args, Returns, Examples, and Error Handling sections. Every sentence is informative and front-loaded with the core purpose. No 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?

Given the tool's complexity (sync operation), the description covers necessary context: prerequisites (agent ID), proper usage, error scenarios, and return format. It also references a sibling tool for checking, making it self-contained for an AI agent.

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 coverage is 100%, but the description adds value with examples (e.g., 'example: agt_abc123', skill list example) and clarifies that desiredSkills must be valid skill names. This enhances understanding beyond the schema's property descriptions.

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 the verb 'Sync' with resource 'agent's installed skills to match the desired list, adding or removing as needed.' This distinguishes it from sibling tools like paperclip_get_agent, which is for checking only. The purpose is specific and unambiguous.

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?

Explicit 'Use when' and 'Don't use when' sections provide clear context for when to invoke this tool versus alternatives. Additionally, the error handling section guides the agent on common failures and resolutions.

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