op3_show_downloads

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

No annotations are provided, so the description must carry the full burden. It describes the output shape (monthly, weekly breakdown, average) but does not disclose whether the operation is read-only, any authentication requirements, rate limits, or data freshness. With no annotations, this is a significant 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 two sentences, front-loading the core functionality and then providing usage guidance. Every sentence adds value with no wasted words.

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 tool is simple with one parameter and no output schema, the description gives a decent overview of what is returned. However, it lacks detail on the exact format of the 'week-by-week breakdown' or the structure of the summary. For a tool with no output schema, more detail would be beneficial.

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 coverage is 100% with the single parameter described in the schema. The description adds value by specifying the UUID comes from op3_get_show, providing context beyond the schema's description of '32 hex chars.'

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 it retrieves a show's recent download summary including monthly downloads, week-by-week breakdown, and average weekly downloads. It distinguishes from siblings like op3_downloads_timeseries by focusing on a summary rather than a timeseries.

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 explicitly states 'Use this for 'how many downloads does my show get' questions' and notes the prerequisite of obtaining a show UUID from op3_get_show. It provides clear context but does not specify when not to use it or mention alternatives explicitly.

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