get_current_app_info

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

Discloses caching behavior via ignore_cache parameter, criticality as first step, and indicates it does not modify state (implied by 'get'). Could explicitly state it's read-only, but overall good for no annotations.

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?

Front-loaded with purpose, uses bold for critical instruction, and organizes usage with numbered points. Slightly verbose with the general label, but every sentence adds value.

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?

Lists returned fields but does not specify return format, error conditions, or how to interpret 'no app selected' state. For a tool that gates other operations, more detail on return value would be valuable.

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 covers the single parameter (ignore_cache) with full description. The tool description does not add extra meaning beyond the schema, but the baseline is appropriate due to 100% schema coverage.

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?

Clearly states the tool retrieves current selected app/game information with specific fields (developer_id, app_id, miniapp_id, app name). Differentiates from siblings by emphasizing it's a prerequisite for leaderboard operations and other tasks.

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?

Explicitly provides when to use (before leaderboard ops, building preview links, verifying cached app) and when not to (H5 upload workflow). Also instructs on alternative flow if no app selected, referencing sibling tools.

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