Get XDaLa payload term statistics

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

No annotations are present, so the description carries full behavioral burden. It only states 'Do not sample sessions', implying the tool processes all sessions, but does not disclose side effects, permission requirements, rate limits, or whether it is read-only. The 'get' prefix suggests idempotence, but that is implicit.

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 three focused sentences, front-loading the usage trigger and providing a key example. Every sentence adds value with no redundancy or verbosity.

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 the tool's complexity (7 parameters, no output schema, no annotations), the description is incomplete. It explains the intended use case but lacks details on return format, parameter interactions (e.g., mode: keys vs values vs keys_and_values), and behavior over large time ranges. The agent is left guessing about important constraints.

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 0%, yet the description only adds meaning for windowHours (example value 336 for 14 days). The other six parameters (owner, outcome, source, mode, minTermLength, limit) are not explained. Their names and enum values provide some hints, but the description does not clarify how they filter or affect results.

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 states the tool retrieves payload term statistics and specifies user queries that trigger it (e.g., 'payload words', 'payload Begriff statistics'). It implicitly distinguishes from siblings like get_xdala_payload_key_stats by focusing on 'terms' rather than keys or values, but does not explicitly contrast.

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?

The description provides explicit use cases ('when the user asks for payload terms...') and an anti-pattern ('Do not sample sessions'). It gives a concrete hint for the common 'last 14 days' request. However, it does not mention alternative tools for sampling or for key/value statistics, leaving the agent to infer from sibling names.

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