list_categories

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

With no annotations provided, the description carries the full burden of disclosing behavior. It only states the action, omitting details such as pagination (despite the continuation parameter), response format, or any rate limits. The term 'standard' is ambiguous and unexplained.

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 extremely concise, but conciseness here borders on under-specification. It is a single sentence with no additional structure or detail, which is acceptable for a trivial tool but fails to leverage the opportunity to add value.

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 existence of an output schema (not provided), the description could rely on it for return values, but it does not address pagination, the meaning of 'standard,' or how this relates to other category tools. Without annotations, the description is insufficient for an agent to confidently invoke this tool in a complex workflow.

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 explain the 'continuation' parameter, but it does not. The parameter name hints at pagination, yet the description provides no context on how to use it, leaving the agent without essential information.

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 verb 'List' and the resource 'standard Eventbrite event categories.' It distinguishes from siblings like get_category (single) and list_subcategories (sub-level) implicitly by the word 'categories,' but it does not explicitly differentiate or mention alternatives.

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 on when to use this tool versus list_subcategories, get_category, or other listing tools. There is no mention of context, prerequisites, or exclusions, leaving the agent to infer usage from the name alone.

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