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

The description adds valuable behavioral context beyond the readOnlyHint annotation: it returns base64 embedded data, explains the default 'sheet' document (merged tournament document), and notes that 'results' and 'plan' are deprecated pre-merge variants. This is richer than typical annotation-only transparency.

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 concise and front-loaded with the core purpose, followed by usage guidance and parameter details. Every sentence contributes essential information without redundancy, making it highly efficient.

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 the presence of an output schema and annotations, the description fully covers the necessary context: when to use, what it returns, the default document, deprecated options, and an alternative. No gaps remain for a decision-making agent.

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 description provides semantic meaning for the 'doc' parameter that the schema lacks, including the default value and deprecated variants. The tournament_key is already described in the schema, so the description complements rather than repeats. Since schema coverage is 50%, the description adds significant value for the undocumented parameter.

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?

Clearly states the tool returns the printable PDF as a base64 embedded resource, which is a specific verb+resource pairing. The description distinguishes it from get_pdf_link and explains the default document type, making its purpose unmistakable.

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?

Explicitly provides when-to-use guidance: 'use this when the organiser wants the file handed to them and your client cannot fetch URLs.' It also names the alternative get_pdf_link for lighter responses, giving clear criteria for selection.

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