sportsdata_session_stats

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

Annotations already declare readOnlyHint, openWorldHint, and idempotentHint. The description adds meaningful context: data comes from local counters, is session-specific, and 'Nothing here has been sent anywhere,' assuring privacy and non-mutation.

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?

Three sentences, each serving a distinct purpose: what it reports, how to interpret signs of misbehavior, and a privacy/scope note. No filler, well-structured, and appropriate length.

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 no parameters and an output schema present, the description covers all essential information: purpose, usage guidance, and behavioral context. It is fully sufficient for an agent to decide when to use the tool and what to expect.

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 tool takes no parameters and the schema is empty (100% coverage). No parameter description is needed, and the baseline for zero-parameter tools applies, so no additional value can be added here.

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 what the tool reports: per-tool call counts, error rates, error codes, latency buckets, and empty-result counts. It explicitly scopes to 'THIS session', which distinguishes it from the many sports-data sibling tools.

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 says 'Useful when a tool seems to be misbehaving' and provides concrete interpretation examples (AUTH_REQUIRED means missing key, high empty count means no upstream data). This gives the agent explicit guidance on when to invoke it and how to interpret results.

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