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

Annotations already establish readOnly and non-destructive, and the description adds useful behavior: output caps (200 lines/16 KB/500 B per line), redaction of secret-shaped values, and no human approval requirement. It does not discuss pagination or auth, but it is substantially more informative than the annotations alone.

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?

The definition is compact and front-loads the resource, sources, limits, and redaction before the no-human note. Every sentence carries operational information without repetition.

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 four-optional-parameter read tool with no output schema, the description covers the important behavior: process sources, result caps, redaction, and no human approval. The remaining gap is the unexplained since_minutes window and default line count, but the tool is otherwise callable.

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 50%; the description adds the process default (ployz) and the line cap, while server omission and enum choices are already in the schema. It says nothing about since_minutes semantics or the lines default of 100, leaving partial compensation.

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?

The description names the resource (a server's own recent logs) and the selectable daemon/process sources, and 'server's own' implicitly separates it from service_logs. It does not explicitly name the sibling alternative, so it is clear but not maximally differentiated.

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?

It gives no when-to-use/when-not-to-use guidance and never mentions service_logs or server_metrics as alternatives. An agent must infer that this is the server-scoped log tool from the purpose alone.

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