delimit_obs_logs

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

With no annotations, the description must fully disclose behavior. It only says 'Search', implying a read operation, but does not mention pagination, format, allowed query syntax, or any other behavioral traits. This is insufficient for safe invocation.

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?

At 5 words, the description is extremely concise but at the cost of missing critical details. It is under-specified and does not earn its place beyond stating the obvious. A good description would be longer but front-loaded with essential 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 the parameter count (3) and the presence of an output schema, the description should at least hint at return values or log format. It does not. The tool is incomplete without further context, increasing risk of misuse.

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%, meaning no parameter descriptions exist. The description adds no parameter information whatsoever. The agent is left to infer from parameter names alone, which is inadequate for correct usage.

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 tool searches system and application logs. The verb 'Search' and resource 'system and application logs' make the purpose obvious. The '(Pro)' qualifier adds context about licensing. It is distinguishable from siblings like delimit_obs_alerts and delimit_obs_metrics.

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 usage guidelines are provided. The description does not indicate when to use this tool over alternatives, nor does it mention any prerequisites or situational context. An agent has no basis to decide between this and other observability tools.

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