List Admin About Statistics

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

No annotations are provided, so the description carries the full burden of behavioral disclosure, but it only says 'Get App Statistics.' It does not state whether admin privileges are required, whether the operation is read-only, what the response contains, or whether the accept-language parameter changes the output. 'Get' weakly implies a read, but nothing is made explicit.

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?

At three words, the description has no wasted text, but this is under-specification rather than genuine conciseness. It front-loads the action but omits nearly all useful information an agent would need.

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?

Although an output schema exists (which relieves the description of explaining return values), the tool is an admin-facing statistics endpoint with no annotations and an undocumented parameter. The description does not convey admin context, what statistics are exposed, or how the parameter behaves, leaving an agent under-equipped to invoke it correctly.

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 0%, and the description says nothing about the accept-language parameter or how it affects the returned statistics. With zero coverage, the description was expected to compensate but does not.

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 states a verb and resource ('Get App Statistics'), so it is not a tautology, but the scope is vague — it does not say which statistics are included (user counts, storage, activity, etc.). It also fails to differentiate from siblings like list_admin_about and list_households_statistics, so an agent cannot tell what makes this tool distinct.

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?

There is no guidance on when to use this tool versus alternatives. The sibling list contains closely related tools (list_admin_about, list_admin_about_check, list_households_statistics) that could easily be confused with this one, yet the description offers no exclusions, prerequisites, or routing cues.

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