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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety profile is covered. The description adds real context beyond that: the counts are 'live', and the 'upcoming gigs' figure is scoped to the directory/concerts rather than application listings. It does not describe count freshness guarantees or caching, but the annotations lower the bar.

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: the metric categories come first and the disambiguation parenthetical comes last. Every clause carries information, with no filler or restatement of the title.

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 and no output schema, the enumerated categories (members by type, venues, open mics, cities, upcoming gigs) effectively stand in for the missing return shape, which is a real strength. It stops short of guaranteeing the exact response keys or whether counts are paginated/snapshotted, so it is strong but not exhaustive for a schema-less read.

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 under the rubric. There is nothing for the description to disambiguate on the input side, and it correctly avoids inventing filter semantics that the empty schema would not support.

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 (live counts) and resource (platform stats across GigXchange), and enumerates exactly what is counted: members by type, venues, open mics, cities, upcoming directory gigs. It further distinguishes itself from siblings by explicitly noting that open-application gigs live in search_open_gigs rather than here.

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 parenthetical clarifies the semantic scope of the gig counts and routes some queries to search_open_gigs, which is useful disambiguation. However, it never states the general condition for reaching for this tool (e.g. 'use when you need an overview/summary of platform activity'), so usage is only implied rather than instructed.

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