search-logs

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

No annotations provided; description doesn't disclose side effects, permissions, output format, or other behavioral traits beyond basic search. Only says 'search' and 'simpler alternative'.

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, efficient: first sentence states action, second provides context. No unnecessary words.

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?

Lacks description of return format, pagination, or behavior for nested attributes. Adequate for basic searches but incomplete for full context, especially without output schema.

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?

All parameters have schema descriptions (100% coverage). Description adds 'optional attributes' but that's already implied. No extra semantic value beyond schema.

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?

States clearly: 'Search New Relic logs with keyword filtering and optional attributes.' Distinguishes from sibling query-logs by calling itself a simpler alternative.

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 says 'simpler alternative to query-logs for basic searches,' guiding when to use vs. query-logs.

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