get_social_media_accounts

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

No annotations are provided, so the description must disclose behavior. It implies a read-only list operation with no side effects. However, it does not mention potential pagination, rate limits, or authentication requirements. The detail about the deprecated parameter is a positive behavioral hint.

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 sentence that is front-loaded with the action and key instruction. It is concise and contains no extraneous information.

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 simple list tool with one deprecated parameter and no output schema, the description is adequate but not fully complete. It does not describe the return format or address potential pagination. Given the context signals, it meets basic requirements but could provide more detail.

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%, so the description has little to add. The instruction to 'omit network' is redundant with the schema's detailed deprecation note. The description adds no new meaning beyond what the schema already provides.

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 ALL connected social media accounts') and the resource. It differentiates by emphasizing 'ALL' and instructing to omit the network parameter, distinguishing it from any tool that might filter by network.

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 one explicit guideline: omit the network parameter. However, it does not mention when not to use this tool (e.g., when needing accounts for a single platform) or alternatives. The schema's parameter description compensates somewhat, but the description itself is minimal.

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