get_mobile_analytics

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

Annotations already provide readOnlyHint=true and openWorldHint=true, indicating safe, read-only behavior. The description adds value by specifying the type of analytics (e.g., sessions, active users), but does not disclose how results are aggregated or whether data is real-time. No contradictions with 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?

The description is a single, concise sentence that front-loads the tool's purpose. While efficient, it could be slightly improved with structured formatting (e.g., bullet points) for readability. No excess words.

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?

The description provides a high-level summary of the output (sessions, active users, popular applets), which is helpful given no output schema. However, it omits the time dimension controlled by the 'days' parameter, and does not explain default behavior or data recency. Adequate but incomplete for a full understanding.

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% for the sole parameter 'days', so the baseline is 3. The description does not mention the parameter, so it adds no additional meaning beyond the schema. The parameter's role is implied but not clarified.

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 action ('Get mobile app usage analytics') and provides concrete examples of metrics ('sessions, active users, popular applets'), making the tool's purpose unambiguous. It distinguishes itself from sibling tools like 'get_performance_analytics' by specifying 'mobile app' and listing typical mobile analytics.

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 offers no guidance on when to use this tool versus alternatives, such as 'get_performance_analytics' or 'get_pa_dashboard'. There is no mention of context, prerequisites, or exclusions, leaving the agent to infer usage without explicit direction.

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