list_platforms

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

With no annotations provided, the description carries the burden of disclosing behavioral traits. The verb 'List' suggests a read-only operation, but it does not explicitly state that it is side-effect-free or whether any authentication is required. It also doesn't clarify what 'adapter status' entails, leaving some ambiguity.

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?

The description is a single, front-loaded sentence with no filler words. Every word contributes to understanding the tool's purpose, making it highly concise and well-structured.

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?

Given the simplicity of the tool (no params, no output schema), the description adequately conveys what the tool returns: a list of supported platforms and their adapter status. However, it could be more complete by elaborating on the meaning of 'adapter status' or the return format, which would further aid the agent.

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, so schema coverage is trivially 100% and the baseline is 4. The description adds useful context by indicating that the output includes 'supported social platforms and adapter status,' which helps the agent understand what to expect from the call.

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 clearly states the action 'List' and the resource 'supported social platforms and adapter status,' making its purpose unambiguous. It distinguishes itself from sibling tools like login_platform and publish_post, which perform actions on platforms rather than listing them.

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 its use as a discovery tool for checking available platforms and their adapter status, but it lacks explicit guidance on when to use it versus alternatives. There is no mention of 'use this before login_platform' or any exclusion criteria, so the usage context is only implicitly derived from the sibling names.

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