capture_insight

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

No annotations provided, but description discloses side-effect (fires insight.created webhook) and return value. Does not contradict any annotations (none present). Could mention rate limits or error conditions.

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?

Three sentences with no filler. Front-loaded with main action. Every sentence adds value: action, side-effect, parameter guidance.

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?

Given no output schema and moderate complexity, description explains what it does, side-effects, parameter usage, and return value. Missing error handling or rate limits, but annotations absence doesn't penalize heavily.

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% with descriptions, but description adds valuable context: links account_id to get_customer_360, feature_id to pm_meta, explains kind='opportunity' meaning, and notes product_id defaults to primary. Adds meaning beyond schema.

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?

Description clearly states the verb 'Write' and resource 'customer feedback to the spine', specifies return of created insight. Distinguishes from siblings by focusing on capturing feedback vs reading or analyzing.

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 advises to only capture genuine signal and provides guidance on when to use account_id, feature_id, and kind. Implicitly distinguishes from read-only tools like get_customer_360 or pm_meta. Lacks explicit when-not-to-use or alternatives list.

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