mongodb-logs

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

Annotations already declare readOnlyHint=true and destructiveHint=false, covering the safety profile. The description adds context that logs are returned in reverse chronological order (most recent first), but it does not disclose details like the default limit, maximum entries, or behavior when no logs exist. Since annotations cover the main behavioral risk, a score of 3 is appropriate.

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 description is a single concise sentence that conveys the core purpose without extraneous words. It is front-loaded with the verb and resource, making it quickly scannable by an agent.

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 the presence of a fully described input schema (100% coverage) and an output schema, the description sufficiently covers the tool's purpose and scope. For a simple read-only log retrieval tool, this is complete; the schema handles parameter constraints and return format details.

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 the schema fully documents the 'type' and 'limit' parameters. The description adds no additional parameter-level semantics beyond what the schema provides, so the baseline score of 3 applies.

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 tool returns the most recent logged mongod events, using a specific verb (returns), resource (mongod logs), and scope qualifier (most recent). This distinguishes it from sibling tools like find or aggregate, which operate on collections rather than server logs.

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 description provides no guidance on when to use this tool versus alternatives, nor does it mention exclusions or prerequisites. For example, it does not clarify whether this is for server diagnostics vs. database operations, or when a user might prefer a different read tool.

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