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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the description doesn't need to restate safety. It adds genuinely new context beyond annotations: the per-entry field list and the important caveat that terminal command side effects are NOT captured, which prevents an agent from over-trusting the log as a full activity record.

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 sentences, front-loaded with the core behavior, then the returned fields, then the scope caveat. No redundancy and the most decision-relevant caveat is placed last without burying the lead.

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?

Output schema exists so return values needn't be explained, annotations carry the safety profile, and the description covers purpose plus its key limitation. Only the filter/limit behavior is left entirely to the schema, which is a minor gap for a read-only log 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 100%, so ok/tool/limit are already fully documented in the schema; baseline 3 applies. The description adds nothing about filtering or default/max limits beyond what is already structured.

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 ('Returns recent LMCP tool call history from the local audit log') and enumerates the fields each entry contains, so the agent knows exactly what comes back. It doesn't explicitly point at neighboring diagnostics tools (run_diagnostics, lmcp_doctor, submit_diagnostics), so sibling differentiation is implied by subject matter rather than stated.

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?

'Useful for debugging and for reviewing what Local MCP's tools did' gives clear usage context, and the closing sentence defines the boundary condition (incomplete while run_terminal_command is enabled). There is no explicit when-not or named alternative tool, which keeps it below a 5.

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