survey_agent_stats

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

No annotations are provided, so the description bears full responsibility for behavioral disclosure. It only states the purpose and does not mention whether the operation is read-only, requires authentication, or any side effects. For a stats tool, this is insufficient.

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 short sentence, which is concise. However, it is too terse to be fully informative; important details are omitted. It is not wasteful but under-specifies.

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?

With one parameter, no annotations, and no parameter descriptions, the description is incomplete. While an output schema exists, the description does not hint at what the stats contain (e.g., counts, conversion rates, time ranges), leaving the agent guessing about the tool's full capabilities.

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?

The input schema has one required parameter 'survey_id' with no description. Schema description coverage is 0%, and the tool description adds no additional meaning about this parameter (e.g., format, example, or relationship to the stats). The agent has no guidance on how to construct valid input.

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 'Funnel stats for a survey' clearly indicates the tool provides statistical data (funnel metrics) for a given survey. It distinguishes from sibling tools like 'survey_agent_list_forms' and 'survey_agent_get' which focus on retrieval or management rather than analytics.

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?

There is no explicit guidance on when to use this tool vs. alternatives. However, the name and description imply it is for retrieving funnel statistics, and among siblings, it is the only one with 'stats' in its name, so usage context is weakly implied.

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