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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so safety is covered; the description adds the auth requirement ('Needs a signed-in member') and the concrete failure mode ('A key with no member gets the error member_required'), which is genuinely useful pre-call knowledge. It does not discuss rate limits or caching, but those are minor for a cheap read.

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?

Short sentences with the capability stated first, then the trigger, then the prerequisites — well front-loaded. The sentence 'It takes no arguments' is the one that fails to earn its place, being both redundant and misleading.

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 output schema, the description carries the return-value burden and does so by enumerating the four things reported (holds pass, renews/ends, forecasts left, when more come). Auth and error behavior are covered; only the optional `asked` parameter is left unaddressed.

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 claim 'It takes no arguments' is inaccurate: the schema defines an optional `asked` parameter that the schema itself documents thoroughly (verbatim question, omit rather than invent). Saying the tool takes no arguments risks the agent silently dropping `asked`, so the description works against rather than alongside the schema here.

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 pair ('Says whether the signed-in member holds the Desk Pass') and enumerates the exact facts returned: renewal/end date, remaining weekly forecasts, and reset timing. That scope is clearly distinct from the sibling forecast tools (query_team_forecast, query_forecast_results), which concern team or result data rather than the member's own quota.

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 someone asks about their Desk Pass or their forecasts' gives an explicit trigger condition. It stops short of saying when to prefer this over the forecast siblings, but the member-scoped phrasing effectively implies the boundary.

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