get_stats

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

With no annotations, the description carries full responsibility for behavioral disclosure. It notes the tool is paginated but does not describe whether it is read-only, what the statistics include, how default top works, or any limitations. This is insufficient for safe invocation.

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 very short (two fragments), which is concise but lacks necessary detail. It front-loads key words like 'aggregated instance statistics' but omits crucial information. The structure is acceptable given the brevity, but the content is insufficient.

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 complexity (3 parameters with no descriptions, no output schema, no annotations), the description is incomplete. It doesn't explain the output format, default behavior, or how pagination works. The information provided is not enough for an agent to correctly invoke the tool.

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%, so the description must explain parameters. It only vaguely mentions 'per model under an instance (default top)', which relates to the 'path' parameter but is unclear. No explanation for 'limit' or 'cursor' beyond the word 'paginated'. The description adds almost no value to the schema.

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 the tool provides aggregated instance statistics per model, which indicates the resource but lacks an explicit verb like 'retrieve' or 'get'. It mentions pagination and a default 'top' instance, which adds context. However, it does not clearly say what the tool does, making it slightly vague.

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?

No guidance is provided on when to use this tool versus alternatives like get_drivers, get_hierarchy, etc. The description only mentions pagination, but does not distinguish the tool's purpose from siblings or specify prerequisites.

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