List platforms supported by the payout calendar

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

With no annotations provided, the description carries the transparency burden and does disclose that data is live from platformincome.com, returns every tracked platform, and includes platforms with no verified schedule. It does not mention response shape or potential remote-fetch latencies, but these are minor for a simple read-only enumeration.

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?

One sentence delivers the core action, the exact data returned, the source, and the notable edge case (no verified schedule). There is no filler or redundant 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?

For a zero-parameter list tool with no output schema, the description tells the agent what data will be returned and that unscheduled platforms are included. Slightly more detail on the output shape or how to obtain schedule details could help, but nothing essential is missing for selecting and invoking this tool.

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 has zero parameters and schema coverage is 100%, so there are no parameter ambiguities. The description adds no parameter info because none is needed; baseline for 0-param tools is 4.

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?

Description states a specific verb ('Returns') and resource ('every platform id and name currently tracked by platform_payout_calendar'), plus the live origin and special inclusion of platforms without verified schedules. This clearly differentiates it from sibling 'platform_payout_calendar' and 'list_take_home_platforms'.

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 description makes clear it returns identifier data from the payout calendar, implying use when a caller needs the set of tracked payout platforms. It does not explicitly name alternatives or exclusion conditions (e.g., use list_take_home_platforms for take-home platforms), so guidance is implied rather than stated.

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