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

With no annotations, the description carries the full burden, and it does disclose two useful traits: the source-selection fallback (private store vs published snapshot) and 'No execution is triggered,' which implies a safe read. It stops short of permissions, rate limits, or return shape, so it is only partially transparent for a tool with zero annotation coverage.

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?

It is a single compact sentence with no wasted clauses, which is good, but the front-loaded fragment is cryptic jargon rather than a clear statement of purpose. Brevity here reads as under-specification rather than discipline.

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 tool with two undocumented parameters, no annotations, and no output schema, the description is too thin: it omits parameter meaning, expected return content, and any routing guidance. The one genuinely useful fact (no execution is triggered) is not enough to make the definition callable with confidence.

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% for two parameters (run_id, category), and the description mentions neither one – not even that category is required or that run_id is optional. The only oblique hint ('when configured') does not map clearly to any parameter, so the description fails to compensate for the coverage gap.

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 opens with the noun phrase 'Automatic attempts, including failures' – a restatement of the tool name's resource with no verb, so it never actually says what the tool does (retrieve? list? summarize?). It does not distinguish itself from siblings like get_results, get_run, or request_tournament, which an agent could easily confuse with it.

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?

'current private-store state when configured, otherwise a published snapshot' hints at which data source is returned but gives no when-to-use guidance, no prerequisites, and no alternatives among the nine sibling tools. An agent cannot tell from this text whether to call this or get_run/get_results.

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