connected_socials

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

The description claims to find 'all' connected profiles, which conflicts with the openWorldHint annotation indicating the result set may be incomplete. It also adds cost information (0.5 credits per request), but the contradiction is severe.

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 two sentences, front-loading the core purpose and adding the cost in the second sentence. It contains no redundant 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?

While the schema and output schema cover the parameters and return structure, the description does not qualify the 'all' claim to align with openWorldHint, making it incomplete for an agent to understand potential incomplete results. The lack of a when-not-to-use also contributes.

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 schema already describes both parameters (handle and platform) with clear descriptions, and coverage is 100%. The description adds no additional parameter meaning, so baseline 3 applies.

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 uses a specific verb 'Find' with the resource 'all social media profiles connected to a creator' and returns linked accounts across platforms. This clearly distinguishes it from sibling tools like discover_creators or enrich_by_handle, which focus on discovery or enrichment.

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 usage when you have a known creator handle and want to see their linked accounts across platforms, but it does not explicitly state when not to use it or name alternative tools. It provides clear context without exclusions.

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