akai_workflow

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

No annotations present. The description says 'browser' implying read-only, but does not confirm side effects, authorization needs, or output behavior. With zero annotation support, the description leaves safety and behavior ambiguous.

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 short at one sentence; it front-loads the name and category. While concise, it could include more detail without becoming verbose.

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?

No output schema, no annotations, and a minimal description. For a browser tool, one expects at least a summary of what is returned or how to use the parameters. The description feels incomplete.

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 has 2 parameters with full descriptions. The tool description adds no extra meaning beyond the schema. Baseline 3 is appropriate given 100% schema coverage.

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 is a 'workflow profile browser' and assigns a category ('pipeline'). This clarifies the verb (browse) and resource (workflow profiles), but does not differentiate from sibling tools like 'akai_flow' or 'akai_pipeline'.

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 the many sibling tools. The description does not mention alternatives, prerequisites, or exclude scenarios.

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