gateway_telemetry_skill_stats

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

The readOnlyHint annotation already establishes that this is a safe read operation, and the description adds the telemetry:read permission requirement. However, it does not disclose aggregation behavior, filtering semantics, or whether results are paginated, though the output schema mitigates some of this gap.

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 focused sentence with no filler. The action and the key prerequisite are front-loaded, making it easy to parse quickly.

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?

Despite having an output schema, the description leaves eight filter parameters entirely undocumented and provides no guidance on how this tool relates to the other telemetry tools. For a tool with this many optional filters and ambiguous sibling overlap, the description is too sparse to fully support correct invocation.

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 names none of the eight parameters. The parameters are only given titles and defaults, so an agent has no idea what 'days', 'agent', 'skill_pack', 'actor_subject', or 'skill_version' mean or how they affect the result.

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 states a specific action ('Return aggregated assistant skill usage stats') with a clear resource. It is distinguishable from most siblings, though it does not explicitly differentiate itself from gateway_telemetry_usage_summary or gateway_telemetry_usage_report, which may also return aggregated telemetry data.

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 only usage guidance is 'Requires telemetry:read,' which states a permission prerequisite but gives no indication of when to choose this tool over the other telemetry siblings. There is no mention of alternatives, exclusions, or typical scenarios.

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