Update Idea

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

Description clarifies that omitted fields remain unchanged, indicating idempotent behavior consistent with idempotentHint=true. No contradiction with annotations; adds context on return value and proper status usage.

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, front-loaded with purpose, no unnecessary words. Highly efficient and clear.

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?

Despite no output schema, description states it returns the idea. Provides cross-tool guidance (list_ideas, promote_idea) which compensates for missing output details. Complete for the tool's complexity.

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?

Adds significant value beyond 100% schema coverage: explains that id is required, body null clears it, and status should not be set to 'promoted' manually. Provides clarity on enum behavior and alternatives.

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 it updates an idea's title/body/status and returns it. Distinguishes from sibling tool promote_idea by explicitly saying to use that for setting status to 'promoted'.

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 specifies when to use this tool (updating fields) and when not to (use promote_idea for 'promoted' status). Also advises to resolve id via list_ideas.

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