obs_query_logs

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only says 'Run a LogQL query' without stating whether it is read-only, what error behavior occurs, rate limits, or the shape of the response. The lack of any such context leaves the agent uninformed about side effects and operational constraints.

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, focused sentence with a helpful example. It is front-loaded with the primary purpose and avoids unnecessary verbosity. The conciseness is appropriate, though it sacrifices depth for brevity.

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?

The description is minimal and does not cover usage context, expected output (despite having an output schema), or operational details. For a tool with three parameters and several siblings, this is inadequate for an agent to use it correctly without further investigation.

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 illustrates the 'query' parameter with an example but says nothing about 'limit' or 'session_name'. The schema provides defaults but no semantic explanation, and the description fails to add meaning beyond the bare parameter names.

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 action (run a LogQL query) and provides an example. It implicitly targets log data, distinguishing it from metrics or traces siblings like obs_query_metrics and obs_search_traces. The verb-resource pairing is specific and unambiguous.

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 guidance is given on when to use this tool versus alternatives. It does not mention exclusions, prerequisites, or comparison with obs_query_metrics or obs_search_traces. The agent is left to infer the intended use case from the LogQL mention.

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