get_session_stats

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

No annotations are provided, so the description carries the full disclosure burden, and it delivers almost nothing: no indication of what metrics are returned, whether the call is read-only or mutating, or what happens when session_id is empty (the schema default). The word "sanitized" is the sole hint and is never explained.

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?

It is short, but brevity here comes from under-specification rather than efficiency, and the second sentence is spent on a nonexistent parameter. Neither sentence is front-loaded with an actionable statement of what the tool does.

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?

An output schema exists, so return-value detail is excused, but for a session-scoped stats tool the description should at minimum tie session_id to the session lifecycle and indicate that the data is masked. As written, the agent has no basis to call it correctly beyond guessing from the name.

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 single parameter session_id is never mentioned, so the description must compensate and does not. Worse, it explains "mode", which is not a parameter of this tool, actively misdirecting the agent about the input shape.

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?

"Sanitized metrics" is a noun fragment with no verb and no resource anchor; the agent cannot tell from the description that this retrieves statistics for a privacy session. The only distinguishing content is a stray note about "mode", which does not describe the tool's operation at all.

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 when-to-use guidance and no mention of the sibling tools (mask_text, clear_privacy_session, create_privacy_session) that an agent would need to choose between. Nothing indicates whether stats should be pulled before, during, or after a masking session.

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