customerthermometer_get_nps_value

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

With no annotations, the description carries the behavioral disclosure burden. It usefully states the return value is a positive or negative integer and that it applies to the account or filtered responses. However, it does not mention default date ranges, whether results are read-only, or how the filter parameters interact.

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 a single, front-loaded sentence with no filler. It states the action, the resource, the return type, and the scope without wasting words.

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?

The description explains the return value and general scope, which is important since there is no output schema. It does not explain filtering semantics or default behavior, but the 100% schema coverage and simple getter nature make it minimally adequate.

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 the parameters are already documented in the schema. The description adds no additional detail about parameter behavior beyond implying date and blast filtering. This meets the baseline for fully covered schemas but does not exceed it.

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 clearly identifies the operation ('Get the Net Promoter Score') and the scope ('for the account or a filtered set of responses'). It also states the return type as an integer, which helps distinguish it from related metrics like happiness value. However, it does not explicitly differentiate itself from sibling tools beyond naming the metric.

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 is provided about when to use this tool versus alternatives such as customerthermometer_get_happiness_value or customerthermometer_get_blast_results. The description implies it is for NPS retrieval, but it does not state exclusions or preferred conditions.

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