Propose a Boardroom idea

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

No annotations provided, so description carries full burden. Discloses side effect ('Posts an 'idea-created' Boardroom event'). Does not mention permissions, rate limits, or destructive behavior. Adequate but minimal.

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 sentences plus a clause, all front-loaded. No wasted words. Each sentence adds distinct value: action, usage, side effect, required parameter.

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 creation tool with 3 parameters and no output schema, description covers purpose, usage, side effect, and required parameter. Does not explain return value or behavior on duplicates, but sufficient for typical 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 coverage is 67% (agent_id missing description). Description adds that agent_id is required (already in schema) and notes description is optional with max 4000 chars. Does not explain agent_id's meaning beyond 'required'. Adds marginal value.

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?

Clearly states action ('Drops a new idea into the Boardroom Ideas board') and purpose ('so the pack can react and vote'). Distinguishes from todo tools by specifying 'Use when something is too speculative for a todo but worth capturing.' Differentiates from siblings like create_todo and promote_idea_to_todo.

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?

Provides explicit when-to-use guidance ('too speculative for a todo'). Implies alternative (create_todo). States required parameter ('agent_id required'). Does not list exclusions or when not to use, but overall clear.

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