perspective_get_stats

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

The description offers minimal behavioral insight. It does not indicate that the tool is read-only, what side effects occur, or any special requirements (e.g., authentication, rate limits). With no annotations, the description carries full burden but fails to disclose key traits.

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 concise sentence, but it lacks necessary details. It is not tautological, yet it fails to earn its place by omitting critical information about what statistics are aggregated or how the time window is specified.

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 zero parameters, no output schema, and no annotations, the description should compensate by clarifying the tool's semantics. It does not explain what 'stats and distributions' refers to, nor how the time window is defined. The tool is incomplete for an agent to use without further context.

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 no parameters, but the description mentions 'over a time window', implying a temporal parameter exists. This contradiction causes confusion. Baseline for 0 parameters is 4, but the misleading implication lowers the score.

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 'Aggregate stats and distributions over a time window' clearly indicates the tool's function of providing aggregated statistics over a temporal range. While it does not explicitly name the resource ('perspective'), the tool name and sibling tools strongly imply it pertains to perspectives. It distinguishes from siblings like perspective_get (single item fetch) and perspective_list (list items).

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 on when to use this tool versus alternatives. The description does not mention any prerequisites, context, or exclusions, leaving the agent to infer usage without support.

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