get_mobile_analytics

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

Annotations already mark readOnlyHint and openWorldHint, so safety is covered. The description adds the specific metrics returned but doesn't disclose additional behaviors like pagination, filtering, or permission requirements. This is adequate but not rich.

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?

One succinct sentence that front-loads the purpose and key output metrics. No extraneous information.

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?

For a simple read-only analytics tool with one optional parameter and no output schema, the description is reasonably complete. It specifies what data is returned and the annotation covers safety. Minor gap: no mention of output format or default behavior beyond schema.

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 coverage is 100% with the 'days' parameter well-described. The description doesn't add extra parameter semantics, but the baseline of 3 applies since the schema fully documents the only parameter.

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?

Description uses specific verb 'Get' with resource 'mobile app usage analytics' and lists concrete metrics (sessions, active users, popular applets). This clearly differentiates from siblings like list_mobile_applets or get_mobile_app_config which deal with configuration/applets rather than 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 context is clear: this tool is for retrieving mobile app usage analytics. It doesn't explicitly name alternatives or provide exclusions, but the resource type and metrics are specific enough to signal appropriate use versus other analytics tools.

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