akai_outreach

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

No annotations provided, and description offers no behavioral traits. 'Quiet' is ambiguous and doesn't disclose side effects, authentication needs, or rate limits.

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?

Overly concise to the point of being uninformative. Single sentence lacks essential details, prioritizing brevity over clarity.

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 nature as a 'distribution engine', the description is critically incomplete. Missing target destination, operation details, and behavioral impact despite simple schema.

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% with clear parameter descriptions ('CLI arguments', 'Optional stdin data'). Description adds no extra meaning but doesn't contradict.

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 is vague: 'quiet distribution engine' lacks a clear action verb and resource. It doesn't clarify what is being distributed or how, and fails to differentiate from sibling tools like 'akai_distribute'.

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. No context, prerequisites, or exclusions provided.

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