Notify All Extensions

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

With no annotations, the description should disclose behavioral traits like side effects, error handling, or permissions. It only states the action without any mention of system impact, failure modes, or rate limits, leaving the agent uninformed.

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, front-loaded sentence with no redundant words. It efficiently conveys the core purpose and scope.

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 broadcast tool, the description is minimal. It does not explain the return value (though an output schema exists) or when broadcasting might fail. While not severely incomplete for such a tool, it could mention typical use cases or limitations.

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?

The input schema has 100% coverage, so the description need not add much. It omits clarifying parameter meaning beyond schema descriptions (e.g., payload format), but the schema already defines type enum and payload as a generic object. No added value, but adequate.

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 tool's action ('Broadcasts a message') and target ('to all connected browser extensions'), distinguishing it from sibling tools like skippr_notify_project_extensions that target a subset.

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?

While the name and description imply use for broadcasting to all extensions, there is no explicit guidance on when to use this versus alternatives (e.g., skippr_send_to_extension for individual messages). The usage context is implied but not stated.

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