metashunt_measurement_stats

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

No annotations are present, so the description carries the disclosure burden. It does reveal a useful behavioral trait—computation happens server-side and avoids transferring the full dataset—but it does not disclose output shape, edge behavior for empty windows or invalid sessions, or side effects.

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 compact sentence. The primary verb and scope are front-loaded, and the 'without transferring the full dataset' clause adds behavioral value without padding.

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?

For a 3-parameter tool with no annotations and no output schema, the description covers the core purpose but omits important invocation details: timestamp semantics, optional window behavior, and what the caller receives in return. It is viable but not fully complete.

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%, and the description adds no per-parameter meaning. It does not explain the units or format of start_t_us/end_t_us, nor how the required session identifier relates to other session tools. The generic phrase 'session window' is the only link to the parameters.

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 names a concrete operation ('Compute aggregate statistics'), enumerates the exact statistics ('count/mean/std/min/max'), and scopes the tool to a session window. The phrase 'without transferring the full dataset' also helps distinguish it from raw-data siblings like metashunt_slice_log.

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 establishes a clear use context: get summary statistics over a session window rather than raw data. It does not explicitly name alternatives or state when not to use it, so it stops just short of full guidance.

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