search-logs

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

No annotations provided, so description must disclose behaviors. It only states the basic search action with time range filtering. Missing details like read-only nature, authentication needs, rate limits, pagination behavior, or response format. The limit parameter hints at pagination but not described.

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?

A single sentence of 8 words is very concise. While it lacks structured elements like bullet points, it efficiently communicates the core purpose without extraneous content.

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 tool with 7 parameters (3 required), no output schema, and no annotations, the description is too minimal. It doesn't cover expected return values, pagination, or usage examples. The schema covers parameter details but the overall context of using the tool is incomplete.

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%, and the description adds no additional parameter context. Baseline 3 is appropriate since the schema already documents all parameters meaningfully.

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 'Search Datadog logs by query with time range filtering' clearly states the verb ('search'), resource ('Datadog logs'), and scope ('query with time range filtering'). It distinguishes from sibling tools like search-audit-logs or search-ci-pipelines by specifying 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?

No explicit guidance on when to use this vs alternatives. The description implies use for log search but doesn't mention when to avoid or what other tools might be better for specific log types or filtering needs.

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