Update a Boardroom idea

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

With no annotations, the description must disclose behavioral traits. It only indicates mutation (edit) and lists editable fields/statuses, but omits permissions, side effects, or whether it returns the updated idea.

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?

One sentence with inline status values is concise, though slightly longer due to listing all enum values. No front-loading issues.

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?

Missing intent: does not mention idea_id requirement (in schema), whether multiple fields can be updated simultaneously, or the return value. For a 5-parameter update tool with no output schema, the description is 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 coverage is 0%, so description partially compensates by listing editable fields and status enum values. However, it does not explain parameter purposes beyond their names, and redundant 'agent_id required'.

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 it edits an idea's title, description, or status, distinguishing it from siblings like create_idea, list_ideas, and vote_on_idea.

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 like create_idea or promote_idea_to_todo. Does not specify conditions or prerequisites beyond requiring agent_id.

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