peek_get_stats

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

Annotations declare readOnly/idempotent/non-destructive, so the safety profile is covered; the description adds genuinely new behavior: visitor IPs and browsers are never returned (a privacy constraint) and that user approval is required. These go beyond annotations. Doesn't mention pagination or rate limits, so not a 5.

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?

Front-loaded action, then privacy guarantees, then return shape, then sibling routing, then approval requirement – no wasted words. It even specifies the return object fields, adding value efficiently.

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?

For a 2-parameter read tool with rich annotations and full schema coverage, the description covers purpose, privacy constraints, approval requirement, sibling routing, and expected output shape. An agent has everything needed to call 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 coverage is 100% and the slug parameter is fully documented in-schema (including cross-reference to peek_list_pages). The description adds no syntax detail beyond the schema, so baseline 3 applies.

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?

States a specific verb+resource (read how often one Peek page was opened, names visitors gave) and distinguishes itself from peek_get_comments by explicitly routing comments to that sibling. An agent can identify the exact scope and output without ambiguity.

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?

Clearly directs the agent to peek_get_comments for comments, establishing a use boundary. It notes user approval is required, implying a gated usage context. No explicit when-not-to-use beyond the sibling routing, so short of 5.

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