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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description adds genuinely new context: a management-access authorization requirement and the fact that event history is capped at the 20 most recent items. It omits whether history beyond 20 is retrievable or paginated, which keeps it short of 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?

Two short sentences, zero filler. The content scope comes first and the access prerequisite second, so an agent can decide from the opening clause whether this is the right tool.

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?

With no output schema, the description does the work of telling the agent what comes back: configuration, usage, and recent traffic. That is adequate for a two-parameter read tool whose annotations cover the safety profile. The one gap is what happens past the 20-event cap, which an agent may need to know before relying on this as a complete history source.

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 100%, with both id and token documented in the schema itself, so the baseline is 3. The description adds only tangential meaning ('management access' loosely maps to the token parameter) and gives no syntax or format detail beyond 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?

States a specific verb (read) and enumerates the resources returned: mock configuration, usage, and the 20 most recent HTTP calls or WebSocket events. That is far more informative than a tautology like 'inspects a mock API.' It does not explicitly distinguish itself from call_mock_api or delete_mock_api, but the read-only inspection scope is unmistakable.

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 prerequisite 'Requires management access' is stated, which is real usage guidance. However, there is no explicit when-to-use statement or routing to alternatives such as call_mock_api (to exercise the mock) or inspect_monitor (for the analogous monitor resource). Usage must be largely inferred from the name and verb.

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