Notify Project Extensions

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

No annotations provided, so description carries full burden. Only states 'Sends a message' with no disclosure of side effects, permissions, rate limits, delivery guarantees, or error behavior. Lacks depth for a communication tool.

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 with no unnecessary words. Front-loaded with the action verb and resource, making it easy to scan.

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 output schema exists, return values may be documented elsewhere, but description lacks context on prerequisites (e.g., project membership), error handling, or whether delivery is guaranteed. Incomplete for real-world agent use.

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 100%, so parameters are already documented. Description adds no extra meaning beyond schema; baseline of 3 is appropriate as the description does not harm but does not enhance parameter understanding.

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 the action: 'Sends a message to all browser extensions connected to a specific project'. It distinguishes from siblings like skippr_send_to_extension (single extension) and skippr_notify_all_extensions (all projects) by specifying 'connected to a specific project'.

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. The description implies broadcasting within a project, but lacks explicit when-to-use, when-not-to-use, or references to sibling tools like skippr_notify_all_extensions or skippr_send_to_extension.

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