get_leaderboard_integration_guide

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

No annotations provided, so description carries full burden. It highlights that no SDK installation is needed (tap is global object) and that it returns a workflow. It implies a read-only, non-destructive operation, which is sufficient.

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?

Description is short (3 sentences) and front-loaded. The use of emoji and capitals may be slightly excessive, but it effectively emphasizes key points. Could be marginally more concise.

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 output schema, the description states 'returns complete step-by-step workflow,' which is adequate for a guide retrieval tool. It provides enough context for the agent to understand the tool's purpose and output.

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?

With zero parameters and 100% schema coverage, the description adds value by explaining the content (step-by-step workflow) and usage priority. Baseline of 4 is appropriate.

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 it returns a 'complete step-by-step workflow' for leaderboard integration, using a specific verb ('get') and resource. It distinguishes from sibling tools like 'get_ad_integration_guide' by focusing on leaderboard setup.

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?

Explicit directives: 'READ THIS FIRST' and 'Call this BEFORE making any implementation plans.' This tells the agent exactly when to use this tool, providing strong contextual guidance.

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