Get Platform Statistics

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

The description adds context beyond the readOnlyHint annotation by listing the specific metrics returned. However, it does not disclose any additional behavioral traits such as data freshness, performance implications, or response format, which would enhance transparency.

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 sentence with no wasted words. It efficiently conveys the tool's purpose and what it returns.

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 absence of parameters, presence of readOnlyHint, and lack of output schema, the description adequately conveys the tool's role. It could be slightly improved by specifying the return format (e.g., JSON object with keys as listed), but is largely complete for a simple stats query.

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 with 100% coverage, so the description correctly adds no parameter details. The baseline for zero parameters is 4, and no extra value is needed.

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 tool's purpose with a specific verb ('Get') and resource ('NaN Mesh platform statistics'), and lists the included metrics (total entities, agents, reviews, favors, categories). This distinguishes it from sibling tools that focus on specific entities or agents.

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 implies usage for obtaining broad platform-level statistics, which is clear given the sibling tools that target individual entities or agents. No explicit when-not or alternative guidance is provided, but the context makes the tool's role distinct.

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