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

With no annotations, the description alone must convey behavior. It communicates that the result is an informational catalog of platforms with per-platform operation support, and the word 'list' implies a read-only call. It does not explicitly confirm non-mutating behavior, output format, or ordering, but for a zero-parameter listing these omissions are minor.

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?

A single sentence with no filler; it states the resource and the key output detail in one line. The information is front-loaded and every word earns its place.

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 parameterless list tool with no output schema, the description explains the return content well enough to invoke the tool. It could arguably enumerate the six operations, but that is likely domain knowledge and not required for a correct call.

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?

There are zero parameters and schema coverage is 100%, so the description has no parameter details to add. Per the baseline for zero-parameter tools, the definition is adequate.

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 identifies the resource (platforms served by Fetchwire) and the specific information returned (which of six operations each supports). It is clearly distinct from sibling tools like list_routes or search_users, though it lacks an explicit verb and relies on the title 'List platforms' for the action.

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 implies a use case: to discover platforms and their supported operations before picking a platform. However, it does not explicitly state when to prefer this tool over alternatives such as list_routes, nor does it mention any preconditions or follow-up actions.

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