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

The description describes a non-destructive save operation ('save for later') while the annotations declare destructiveHint=true, which is a direct contradiction; the write-tier approval detail is useful but does not resolve or disclose the destructive behavior. Per the contradiction rule, this dimension is scored 1.

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?

The purpose is front-loaded, and each part adds distinct value: trigger, exclusion, and approval behavior. The bracketed write-tier block is dense but necessary; slight redundancy between 'Capture an idea' and 'Use when user shares an idea' keeps it from a 5.

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 3-parameter create tool, the description covers why and when to use it and the approval flow, which is most of what an agent needs. It is incomplete because it contradicts destructiveHint, and the companyId parameter's relevance to 'user's Ideas' is unexplained.

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 100%, so the schema already explains content, companyId, and source_url. The description adds no new parameter-level meaning beyond calling content an 'idea' and does not clarify whether/why companyId is needed for this personal Ideas tool; baseline 3 is appropriate.

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?

Opens with a specific verb and resource: 'Capture an idea into the user's Ideas.' It then gives the trigger condition ('user shares an idea they want to save for later') and explicitly contrasts with save_knowledge, so an agent can tell it apart from its nearest sibling without inspecting schemas.

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 states when to use ('use when user shares an idea...') and when not to ('Sitting debriefs and company notes are save_knowledge, not Ideas'). It also adds operational guidance on approval: when to call, what counts as approval, and not to re-ask in chat.

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