start_brew

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

No annotations provided. Description implies it starts brewing but does not disclose side effects (e.g., stopping previous brew) or state changes. Adequate but could be more detailed.

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?

Two concise sentences with no superfluous information. Each sentence serves a purpose.

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?

Covers prerequisites but lacks details on success/error behavior, return format, and what happens if conditions are not met. Adequate for a simple action.

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?

No parameters (schema empty). Description adds context about using the currently loaded profile, which is helpful. Baseline 4 due to 0 parameters.

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 action (start brewing) and the resource (espresso using the currently loaded profile). It distinguishes from siblings like stop_brew and load_profile.

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?

Explicitly mentions preconditions: machine ready and profile loaded. Does not mention when not to use or alternatives, but for a specific action this is sufficient.

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