customer_success_nps_action_loop

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

No annotations are provided, and the description only mentions routing through a dispatcher with JWT/tenant/company scope. It does not disclose whether the action creates data, sends messages, or has side effects. The behavioral impact is completely opaque.

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 description is short and no-frills, but it lacks substance. Conciseness is achieved at the expense of informational value, making it minimally acceptable but not well-structured for an AI agent.

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?

Although an output schema exists, the description does not mention what the tool returns or how to interpret results. The tool appears to be a generic action runner, but the description omits critical details like success/failure behavior, expected outcomes, or dependencies.

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 the description bears full responsibility. It labels 'message' as 'Free-text objective' and 'inputs' as 'Optional JSON string of structured inputs', which adds minimal clarity. No explanation of expected format, values, or constraints for either parameter.

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 only states 'Run the customer_success domain agent action nps_action_loop' and mentions routing details, but fails to explain what the action actually does (e.g., send NPS surveys, analyze feedback). It is a tautology that restates the name without providing meaningful purpose.

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 other customer_success tools (e.g., customer_success_chat, customer_success_health_score_report). No alternatives, prerequisites, or context for selection.

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