Things To Do API

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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world behavior, so the safety profile is covered. The description adds useful context beyond them by enumerating the breadth of the returned record (tags, venue, links, times), signalling 'complete, unfiltered fetch' rather than a summary view.

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?

One sentence, zero padding, with the scope ('one event', 'in full') and the id source front-loaded. Every clause earns its place.

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?

There is no output schema, so the description usefully enumerates the returned fields, which is what an agent needs to know to call it correctly. It could say more about error behavior when an id is unknown, but for a single-parameter lookup it is close to complete.

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 0% and the schema itself is just a bare 'id' string, but the description supplies the provenance that makes the parameter usable — the id originates from search_events. That is meaningful guidance not present in the 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?

States a specific verb and resource ('Everything known about one event by its id') and scopes it to a full single-record fetch. The parenthetical '(from search_events)' distinguishes it from the sibling that produces the ids, so an agent can route between them without opening either schema.

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 phrase 'by its id (from search_events)' makes the intended workflow clear: obtain an id from search_events, then call this. It does not state when NOT to use it or name alternatives for other lookups, so it falls short of full exclusion guidance.

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

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is fully covered by structured data. The description adds only that the content is a coverage catalog (metros, cities, categories) and says nothing about size, pagination, or freshness of the list. With annotations carrying the burden, a 3 is appropriate.

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?

Two short sentences with zero filler: the first states what is returned, the second states when to call it. Front-loaded and appropriately sized for a no-argument lookup tool.

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 no parameters, no output schema, and full annotation coverage, the description only needs to say what data comes back and when to call it — both of which it does. It could be slightly stronger by noting the granularity (e.g., whether results are grouped by metro or flat), but nothing essential is missing.

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 tool takes zero parameters, so the baseline is 4; there is no parameter syntax for the description to clarify. No misleading parameter hints are present.

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 names the exact resource returned (metros, cities, and categories), so an agent knows this is a static coverage catalog rather than an event lookup. It lacks an explicit verb like 'list' and does not contrast itself with get_event or search_events, but the resource is specific enough to be distinguishable.

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?

'Call it when unsure whether a city is covered' gives a concrete triggering condition, which is exactly the right guidance for a reference-lookup tool. It does not name alternatives or exclusions, but the sibling tools (get_event, search_events) are clearly different operations, so no routing ambiguity remains.

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

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

Goes well beyond the annotations (which only cover read-only/idempotent/safety): it discloses the return shape (start times in local timezone, venue, summary, tags, ticket and source links, match reasons), the geographic coverage boundary and what happens outside it, and the pagination contract via next_offset. No annotation contradiction — openWorldHint=false is consistent with the explicit Bay Area-only coverage.

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?

Front-loaded with purpose, then progressively narrower guidance on query phrasing, structured params, returns, coverage, and pagination — a logical order. It is a dense block of text and the three quoted query examples are repetitive in form, but each sentence carries actionable content for a free-text search tool, so waste is limited.

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?

For a 9-parameter, zero-required, free-text search tool with no output schema, the description supplies everything an agent needs: what to put in `query`, when to use the structured filters instead, what a result contains, the coverage boundary, and how to page. Nothing material is left to inference.

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 already 89%, so the baseline is 3, but the description adds real meaning the schema does not: `query` may itself contain when, where, and who the search is for, with worked examples, and the 'who it is for' phrasing ('comedy this weekend for my parents, they hate crowds') is nowhere in the schema. It also restates the precedence of `from`/`to` over time in the query and the meaning of `near`/`place` as exact-knowledge alternatives.

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?

States a specific verb and resource ('Find events happening in a city') and immediately enumerates the domain (concerts, club nights, comedy, markets, festivals, classes, exhibitions), which separates it from the single-event `get_event` and the coverage-listing `list_coverage` without the agent needing either schema. The scope statement ('Covers the San Francisco Bay Area today') further pins down exactly what this tool does and does not return.

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?

Gives clear routing rules for the free-text vs structured parameters: pass plain words in `query`, use `from`/`to`, `place` or `near` 'when you already know them exactly', and continue with `offset` for more results. It also flags the failure mode (place outside the Bay Area returns not covered). It stops short of naming sibling tools or stating when-not to call this one, so it is clear context rather than full when/when-not/alternatives guidance.

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