paperclip_list_company_skills

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

Describes return format (pagination envelope) and states it returns up to 50 skills per page. Error handling adds context. Annotations already declare readOnlyHint, so description adds useful detail 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?

Very concise: one-line intro, structured return, usage examples, and error handling. No wasted words, each sentence serves a purpose.

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 listing tool with pagination, the description covers purpose, when to use, return structure, and common errors. No missing elements given the low complexity.

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%, so schema already describes parameters. Description does not repeat parameter details but reinforces pagination behavior (up to 50 skills per page). Adequate but no significant added value beyond schema.

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 'List all skills installed at the company level', using a specific verb and resource. It distinguishes from sibling tool paperclip_get_agent by noting when not to use this tool.

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?

Provides explicit 'Use when' and 'Don't use when' with a named alternative (paperclip_get_agent). Also includes error handling tips for authentication and permission issues.

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