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

Annotations already establish readOnlyHint, non-destructive and closed-world, so the safety profile is covered. The description adds genuinely new behavior: ordering (newest first), the meaning of each status including the retention window 'until setupUntil' with automatic re-check, and a privacy boundary that email text, headers and addresses are never exposed.

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?

Information is front-loaded — resource, ordering, and source of truth come first, then the status vocabulary. It is a single dense sentence with nested parentheticals rather than a run-on of filler; every clause carries substance, though splitting the status list from the privacy note would improve scannability.

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?

An output schema exists, so the description does not owe the agent a return-value inventory, yet it still explains the state machine semantics (setting_up retention and re-check) that a schema cannot convey. Combined with the privacy statement and ordering, an agent has enough to call and interpret this correctly; only explicit sibling routing 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 there is nothing for the description to disambiguate and the baseline of 4 applies. The schema is closed with additionalProperties false, and the description correctly implies no filtering inputs are needed.

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 resource and its scope: the status of each ticket email the connected fan submitted, newest first, with an enumerated set of states. It clearly differs from submit_ticket_email (writing) and get_fan (the fan record), though it never names those siblings explicitly.

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 implied rather than stated — an agent can infer this is the read path for tracking submitted emails, and the 'setting_up ... checked again automatically' note hints that polling is unnecessary. But there is no explicit when-to-use or when-not-to-use, and no routing to siblings such as get_fan or request_inbox_check.

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