get_platform_info

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It indicates a read-style operation via 'Get' but does not explicitly state it is read-only or safe, nor does it describe any edge cases (e.g., behavior when no platforms are connected) or what 'limits' includes. This leaves room for 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 concise sentence that immediately states the tool's purpose. It is front-loaded with the verb and object, with no unnecessary words or repetition.

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 tool with no output schema, the description covers the core functionality adequately. However, it could be more complete by specifying what kinds of limits (e.g., rate limits, character limits) and whether connected platform details include account names or IDs. Still, given the tool's simplicity, the description is mostly sufficient.

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 the description does not need to explain parameter meanings. The baseline for zero-parameter tools is 4, and the description adds value by naming the output scope (platforms and limits) which helps set expectations.

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 tool's function: fetching combined platform information and limits. It uses a specific verb ('Get') and resource ('all connected platforms'), distinguishing it from sibling tools focused on posts, accounts, or publishing actions.

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 provides clear context for when to use the tool (when needing platform information and limits), though it does not explicitly name alternatives or exclusions. Given the tool takes zero parameters and has no close siblings, this is sufficient guidance.

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