Clipboard URL → Reading List

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

Annotations already provide readOnly, non-destructive, idempotent hints. The description adds that it 'listens' implying a monitoring behavior, but doesn't clarify what happens after a URL is detected (e.g., does it add to a reading list automatically?). No contradiction with 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 a single incomplete sentence. It is too short to be informative and lacks proper structure. Not a model of conciseness; it's under-specified.

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?

With no output schema and zero parameters, the description should at least complete the action. The truncation leaves the core behavior undefined. Incomplete context for a skill that likely has side effects beyond reading.

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?

Input schema has no parameters, so description doesn't need to explain them. The absence is clear from schema. Baseline score applies.

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 states it listens for clipboard changes and acts on URLs, which clarifies the title, but the sentence is truncated and does not fully specify the action. It vaguely distinguishes from sibling skills but lacks completeness.

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 versus alternatives like set_clipboard or other skills. The description does not specify prerequisites or context.

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