search-logs

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

With no annotations, the description carries full burden. It mentions that returns actual log messages, which is useful. However, it does not disclose behavioral traits like pagination limits, cursor usage, or rate limiting. The parameters page and limit are present in schema but not explained, leaving gaps.

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 extremely concise—two sentences that front-load the purpose and then deliver usage guidelines and alternative. No redundancy or irrelevant information.

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 no output schema and 4 parameters with nested objects, the description covers purpose and usage but lacks details on pagination, result limits, and output format. For a search tool, it is adequate but not comprehensive.

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 0%, so the description must compensate. It provides query syntax examples and time range format for the filter sub-properties, but does not explain sort, page, cursor, or limit parameters. Partial coverage, baseline 3.

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 'search and retrieve', the resource 'log entries from Datadog', and provides specific example use cases. It distinguishes from the sibling tool 'aggregate-logs' by mentioning its alternative use.

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?

Explicit guidance is provided with concrete examples ('find errors in auth service', 'show logs from last hour'), query syntax, and time range format. It also explicitly states when to use an alternative ('Use aggregate-logs for counts/stats instead'), offering clear decision support.

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