get_current_app_store_snapshot

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

No annotations are present, so the description carries the full burden. It explains the prerequisite and the return content (a comprehensive snapshot). The tool is read-only by nature (get), but it does not explicitly state that it has no side effects. Still, the behavioral context is well covered.

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: the first is a critical prerequisite note, the second lists the return contents. No unnecessary words, and front-loads the most important usage condition.

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 lists the types of information in the snapshot (e.g., app card info, stats, rating summary, trend, version status, visibility). It also covers the prerequisite for using the tool. This is complete for the tool's purpose.

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 input schema has no parameters, so the description's job is trivial. However, the description adds value by explaining what the snapshot includes, which is more than the schema provides. Baseline for 0 params is 4, but the extra context justifies a 5.

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 that the tool gets a store snapshot for the currently selected app, listing specific included data (app card info, stats, rating summary, 30-day trend, version status, visibility). This distinguishes it from siblings like get_current_app_info or get_current_app_review_overview.

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 prerequisites are provided: an app must be selected first, and the user is guided to call get_current_app_info and, if needed, a sequence of steps including list_developers_and_apps and select_app. This tells the agent exactly when and how to use the tool.

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