get_current_app_community_overview

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

With no annotations provided, the description carries full burden for behavioral disclosure. It mentions optional date range and lists returned metrics, but does not clarify authorization needs, error behavior (e.g., if no app selected), or whether the operation is read-only.

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 extremely concise with two sentences. The first sentence front-loads the critical prerequisite in bold, and the second sentence efficiently states the purpose and scope. Every sentence adds value without redundancy.

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 the moderate complexity (two optional parameters, no nested objects), the description adequately covers the tool's function and output metrics. However, without an output schema, it could better describe the structure of trend data or any pagination, leaving minor gaps.

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%, so the baseline is 3. The description adds no extra meaning beyond what the schema already provides (date range), merely referencing 'optional date range' without further detail.

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 identifies the tool as retrieving community overview metrics for the currently selected app, listing specific metrics like topic count and page views. It distinguishes from sibling tools such as get_current_app_info and get_current_app_review_overview by focusing on community data.

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 emphasizes a mandatory prerequisite—an app must be selected first—and advises verifying context before calling. However, it does not provide explicit guidance on when not to use the tool or how it compares to alternatives like get_current_app_forum_contents.

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