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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered; 'It reads only and changes nothing' largely restates that. The description does add non-annotation context: the auth requirement ('needs a connected Phorme account') and the shape of the returned ledger (earned, paid out, going out, owed now, bank setup, recent payouts).

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?

Four sentences, front-loaded with the trigger scenario, then returns, then safety, then prerequisite; each sentence is short and readable. It loses a point for mild redundancy, since 'reads only and changes nothing' duplicates the readOnlyHint/destructiveHint annotations.

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 inputs and an output schema present, the description only needs the trigger, the read-only nature and the account prerequisite, and it supplies all three. Return-field detail is covered by the output schema, so no agent-facing gap remains.

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 (empty object schema, additionalProperties=false), so there is nothing for the description to disambiguate. Baseline 4 applies; no parameter meaning is missing.

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?

Names a specific verb+resource+scope ('what Phorme paid them', earned/paid/owed ledger for the account) and anchors it with a concrete user utterance ('what did Phorme pay my gym?'), which separates it from the reporting sibling get_gym_report and the link-generating get_payout_setup_link. An agent can identify the tool without opening the schema.

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?

Gives an explicit trigger ('Use this when an owner asks what Phorme paid them, or what goes out next') plus the prerequisite of a connected Phorme account. It does not name a specific alternative to use instead, e.g. get_gym_report or get_payout_setup_link, so exclusion guidance is absent.

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