show_extras

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

No annotations are present, and the description is a noun-phrase definition rather than an action statement. It does not explicitly disclose read-only behavior, side effects, authentication needs, or rate limits, so the invocation behavior is not clearly transparent.

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 short sentence with no unnecessary words or redundant information. It is well-structured and easy to parse.

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?

The description is adequate for a simple one-parameter tool, but it lacks the date format, return structure, and usage context. It is not severely incomplete, but it is not fully self-sufficient for an agent deciding whether and how to invoke it.

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 only parameter, date, is referenced as 'a given date', giving some context that it is the show date. However, the description does not specify the expected date format or any constraints, leaving some ambiguity beyond the schema's basic string type.

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 identifies the resource being accessed (poster art, images, and external links attached to a show) and references the date parameter. It is distinguishable from sibling tools by focusing on show extras rather than setlists, history, or stats, though it lacks an explicit verb such as 'retrieves' or 'lists'.

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?

No guidance is provided about when to use this tool versus the sibling tools, or when not to use it. The description only states what content is involved, not the circumstances under which the tool should be selected.

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