get_stats

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

No annotations are provided, so the description must carry the transparency burden. It reveals that the tool is a read operation returning a set of metrics, which implies safety but does not explicitly state whether it is idempotent or has side effects. It gives some behavioral context but lacks details on rate limits, permissions, or return format.

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, making it concise. It front-loads the purpose and lists key return values. However, it is slightly under-specified because it omits parameter details; it is efficient but not fully informative.

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 lack of output schema and low parameter coverage, the description is the sole source of information. It lists some return metrics but omits data types, error conditions, and usage context. For a stat retrieval tool, it is incomplete and could be more helpful with additional details.

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 sole parameter 'sessionId' has no description in the input schema (0% coverage). The tool description does not mention the parameter or explain its format, constraints, or purpose. The description adds no value beyond what the schema already provides, which is nothing.

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 purpose: checking the current state of a session, listing specific metrics like prototype count, μ, ignition count, steps, and context pollution. It is specific about what the tool does, though it does not explicitly differentiate from siblings like dump_prototypes or get_calibration, which likely have distinct purposes.

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 provides no explicit guidance on when to use this tool versus alternatives. It does not mention prerequisites, conditions, or exclusions. The meaning of 'session state' is implied but not detailed enough to help an agent choose between this and siblings.

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