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

No annotations are provided, so the description carries the burden. 'Get' safely implies read-only and the supported-city scoping is stated, but it says nothing about behavior when the slug is valid for a different city, when no gig matches, or what the response contains. That is a meaningful but not severe gap for a simple read operation.

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?

A single front-loaded sentence with the resource and both scoping constraints and no filler. It is appropriately sized for a two-parameter lookup, though it is terse enough that it could have spent one more clause on failure behavior without becoming bloated.

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 simple two-parameter lookup with no annotations and no output schema, the description covers what is needed to invoke it but leaves the return shape and not-found behavior unstated. Given the absence of an output schema, a brief note on what a successful or failed lookup yields would round it out.

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 100% and the city enum is fully enumerated in the schema, so the schema already documents both parameters. The description restates the same scoping (slug + supported city) without adding format, case-sensitivity, or matching semantics, so the baseline 3 applies.

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 a specific verb and resource ('Get one gig') and scopes it to a slug within a supported city, which cleanly separates it from the batch-oriented sibling search_gigs_and_events. It does not explicitly name that sibling as the alternative, but the single-item retrieval intent is unambiguous.

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?

Usage is only implied: the phrase 'by its slug within a supported city' signals that the caller must already know the slug and city, which is the de facto precondition. There is no explicit when-to-use/when-not guidance or reference to search_gigs_and_events for lookup-by-criteria, so an agent must infer the routing.

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