lattice_get_database_logs

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

The description states it returns stdout/stderr, but with no annotations, it lacks detail on behavior such as log ordering, pagination limits, permission requirements, or that logs are real-time or historical. It is not misleading but could be more transparent.

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 filler: first states purpose, second provides usage context. Every word 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?

With no output schema and 3 parameters, the description is adequate for a simple log retrieval tool but does not explain return format, pagination, or how to interpret the logs. Could be more complete given the complexity of diagnosing failures.

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 100%, so parameters are documented in the schema. The description adds no additional meaning beyond the schema, which is acceptable per baseline guidelines.

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 action ('Get a database container's stdout/stderr') and the resource ('database container'), distinguishing it from sibling `lattice_get_database_events` by contrasting logs vs events.

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 recommends using together with `lattice_get_database_events` for diagnosing failed instances, providing clear usage context. However, it does not mention other alternatives like `lattice_get_database_lifecycle_logs` or container log tools.

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