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

With no annotations, the description carries the full burden, and it does disclose meaningful traits: it is free, it returns sourced facts with a check date, and it explicitly disclaims legal/tax advice. It doesn't state whether the call is read-only or note rate limits, but for a clearly-named lookup this is solid coverage.

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?

Front-loaded with the usage condition, then a compact list of what is returned. Every phrase carries information; the enumerated list is dense but appropriate given there is no output schema to convey the return shape.

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 usefully enumerates the returned facts, which is exactly what an agent needs here. One param fully documented, usage precondition stated, disclaimer included — little is missing for a single-id lookup 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?

Schema coverage is 100% and the single 'id' parameter already enumerates all valid platform ids, so the schema does the heavy lifting. The description adds no format or constraint detail beyond it, which is the expected baseline for fully documented params.

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 ('get') and resource ('platform'), then enumerates the exact payload (rules, human steps, KYC, fees, payout minimum, ban reasons, sources, check date). The phrase 'Use when you already picked a platform' implicitly contrasts with list_platforms, though no sibling is named outright.

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?

'Use when you already picked a platform' gives a clear precondition that separates this from list_platforms or recommend. However, it never explicitly names those alternatives or states when-not to use it, leaving the routing to inference.

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