Read the local audit log

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

Annotations already declare readOnlyHint and openWorldHint=false, so safety is covered; the description adds genuinely useful behavior: append-on-every-call, timestamp/args/outcome fields, and secret redaction at write time. It omits pagination and limit behavior, keeping 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?

Three dense sentences, front-loaded with the core action and scope, followed by the record contents and filters. No filler, no repetition of the title.

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 usefully describes what each log entry contains and how filtering works. The only missing piece an agent needs to call it correctly is the limit/pagination semantics, which is minor for an optional read 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 compensate. It documents two of three parameters well (tool name filter, outcome enum values), but never mentions 'limit' or its default of 50 and max of 500, leaving a real gap.

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 and resource ('Read this server's own call log') with scope and ordering ('newest first'), and explicitly contrasts with the Telegram-facing siblings ('nothing is read from Telegram'). An agent can distinguish it from telegram_audit_summary and the rest of the catalog without inspecting schemas.

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?

Gives clear context for when this applies (inspecting this server's own call history) and lists the optional narrowing filters with the accepted outcome values. It does not explicitly name the sibling alternative (telegram_audit_summary) or state when-not to use it, so it falls short of a 5.

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