check_all_platforms

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

No annotations are provided, so the description carries the full burden. It mentions checking 'availability' but lacks details on behavioral traits like rate limits, authentication needs, error handling, or what 'availability' means (e.g., real-time vs cached results). The description adds minimal context beyond the basic purpose.

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 front-loaded with the core purpose in the first sentence and adds a usage guideline in the second. Both sentences earn their place by providing essential information without redundancy or fluff.

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 no annotations and no output schema, the description adequately covers the purpose and usage but lacks details on behavioral aspects like response format, error cases, or platform-specific nuances. It's complete enough for a simple lookup tool but could benefit from more transparency.

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 description coverage is 100%, with the parameter 'username' well-documented in the schema. The description adds no additional meaning beyond implying the parameter applies to all platforms, which is already clear from the tool's purpose. Baseline 3 is appropriate as the schema does the heavy lifting.

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 specific action ('check username availability') and resource ('across all supported platforms'), explicitly listing the platforms (YouTube, TikTok, Threads, X, Instagram). It distinguishes from sibling tools by emphasizing 'all at once' versus individual platform checks.

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 explicit guidance on when to use this tool ('Perfect for comprehensive brand name research'), contrasting with sibling tools that check individual platforms. It implies an alternative approach (using individual tools) without naming them directly.

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