query-logs

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

No annotations are provided, so the description must carry the full burden of behavioral disclosure. It only says 'query', which implies a read operation, but it does not explicitly state read-only behavior, authentication needs, rate limits, or potential costs. The lack of detail could lead to misuse for a data retrieval tool.

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 sentence that front-loads the core action ('Query New Relic logs'). It is concise with no unnecessary words. However, it could be slightly more informative without losing conciseness, such as specifying the default time range.

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 9 parameters (time ranges, conditions, selection) and no output schema, the description is too generic. It fails to explain behavior like default time windows, how 'queryField' and 'queryValue' interact, or what the return format looks like. This is insufficient given the tool's complexity.

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 each parameter is already documented. The description adds no extra meaning beyond the schema, merely saying 'by field and value with customizable parameters'. This meets the baseline for high-coverage schemas but adds no additional value.

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 it queries New Relic logs by field and value, which is a specific verb-resource combination. It distinguishes itself from the sibling 'run-nrql-query' by implying a simpler, field-specific query rather than a general NRQL query.

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 the sibling 'run-nrql-query'. It does not mention when not to use it or any prerequisites, leaving the agent without decision support for tool selection.

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