get_log

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

With no annotations provided, the description carries the full burden. It discloses an important behavioral nuance: the timestamp is required and used to narrow the search window. However, it does not detail other behavioral traits such as what happens if the log is not found, the return format, or potential performance implications.

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, focused sentence that wastes no words. It states the core purpose and the key requirement in a clear, front-loaded manner.

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 simple two-parameter retrieval tool with no output schema, the description plus schema provide a solid understanding of how to invoke it. The main gap is the lack of detail on the return value or error behavior, but these are not critical for basic invocation. Overall, it is sufficiently complete for an agent to select and use the tool correctly.

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 already explains both parameters. The description adds slight emphasis on the word 'approximate' for the timestamp, but this is already present in the schema's parameter descriptions. Therefore, no significant additional meaning is conveyed.

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 'Retrieve a specific Datadog log entry by its unique ID', which is a specific verb+resource+scope. The word 'specific' distinguishes it from sibling tools like search_logs and aggregate_logs, which handle broader queries.

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 a clear prerequisite: 'Requires the approximate timestamp of the log to narrow the search.' This sets the context for when to use this tool (when you have the log ID and an approximate timestamp). However, it does not explicitly mention alternatives or when not to use it, like 'for broad searches, use search_logs'.

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