analyze_nps

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

No annotations provided, so description should disclose behavioral traits. It mentions computation and data joining, but does not explicitly state read-only nature, access requirements, or any side effects. For a read analysis, it's adequate but not thorough.

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?

Description is two sentences, front-loading the main output. The first sentence is long but packs information efficiently. Could be slightly cleaner but overall concise.

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, description mentions detractor accounts and verbatims but lacks structured return details. For a moderately complex tool, it covers the key outputs but could benefit from more explicit return format.

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 description coverage is 100%, so description adds little beyond stating defaults. It mentions product_id optional and window_days default, but that's also in schema. No additional meaning.

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 it computes standard NPS and revenue-weighted NPS, plus detractor accounts and verbatims. It distinguishes from sibling tools like analyze_nrr by focusing on NPS rather than revenue retention.

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?

Description explains the value of the revenue-weighted feature, hinting at when it's useful (when biggest customers are unhappy despite good headline score). No explicit alternatives or when-not, but the use case is clear.

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