get_logs

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

The description discloses that logs are ephemeral and not persisted across restarts, which is a key behavioral trait. No annotations are provided, so the description carries the full burden; it does well but could mention potential performance impacts or read-only nature.

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 sentences with no wasted text. The primary action is front-loaded, followed by usage guidance and behavioral context. Every sentence earns its place.

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?

Given two parameters, no output schema, and no annotations, the description covers purpose, usage context, and ephemeral nature. It could mention the return format or that limit controls the number of entries, but overall it is sufficiently complete for a diagnostic 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?

The description mentions the 'level' parameter with its enum values, adding meaning beyond the schema. However, it does not mention the 'limit' parameter, which has a default of 100. With 0% schema description coverage, the description partially compensates but misses one parameter.

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 clearly states the verb 'return', the resource 'server log entries', and the filtering capability by level. It distinguishes this tool from the sibling 'get_audit_logs', which provides persistent audit trails.

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?

Explicitly states when to use ('to diagnose unexpected tool behavior or connection errors during the current session') and when not to use ('use get_audit_logs for persistent audit trail'), providing clear context and alternatives.

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