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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered and the description adds content scope: screens, pending applications, earnings, withdrawals, payments and reports, plus the next offline setup window and backup WiFi. It does not state auth/account requirements, pagination, or how large a result set to expect, so it goes beyond annotations only modestly.

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?

It is a single front-loaded sentence that opens with the scope, which is good, but the long parenthetical enumeration largely restates what an output schema already exposes. Every item is plausible payload, yet the list is dense enough to be skimmable only with effort.

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?

Because the tool aggregates many domains, the description needs to signal breadth, and it does. With zero parameters and an output schema present, the missing when-to-use routing and account/auth notes are the only real gaps.

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 there is nothing for the description to disambiguate and the baseline applies. It correctly implies the account is derived from the session rather than supplied as input.

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 resource precisely as 'the venues this account hosts screens at', which scopes it to the host role and separates it from advertiser.venues.get and ambassador.venues.list. The verb is implicit (an overview/aggregate read rather than a mutation), but the enumerated contents make the intent 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?

There is no explicit statement of when to call this instead of siblings such as host.earnings.wallet, host.venue.apply, or advertiser.venues.get, and no prerequisites or exclusions. Usage is only inferable from the phrasing 'this account hosts screens at' and the final note about venues without screens.

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