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

The description states it returns shows across years but does not disclose behavior of the optional 'include_related' parameter or any output details. Without annotations, the description only partially covers behavioral traits.

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 sentence that is concise and front-loaded with key information. Every word serves a purpose with no unnecessary text.

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 three parameters, no output schema, and no annotation support, the description fails to explain the behavior of 'include_related', return format, or any constraints like pagination. The tool's functionality is only partially described.

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%, so the description must compensate. It only explains the range for month and day, ignoring the 'include_related' parameter entirely. This adds minimal value over the raw schema.

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 the tool returns shows played on a given calendar day across years. It specifies the verb 'shows played' and the resource 'given calendar day', but does not explicitly distinguish from siblings like search_shows or song_history.

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 implies usage for querying historical shows on a specific date but provides no guidance on when to use this tool versus alternatives like search_shows or jam_chart. No exclusions or alternative suggestions are given.

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