dns_query_logs

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

With no annotations, the description must disclose behavior itself. It mentions that the tool returns recent queries and responses and requires an app installation, but it does not state whether the operation is read-only, how errors are handled, or any rate limits. The 'recent' qualifier adds some temporal context but is not fully detailed.

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 exactly two sentences, front-loaded with the verb 'Query' and the resource, and contains no redundant information. Every word earns its place.

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 six-parameter schema with no output schema and no annotations, the description provides a high-level purpose and prerequisite but lacks details on return structure, the exact time window for 'recent', and filter combination behavior. It is adequate but not fully complete.

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 six parameters are fully described in the schema (100% coverage), so the description adds minimal value beyond that. The phrase 'optional filters' is only a generic summary and does not clarify parameter usage or relationships beyond the 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?

The description clearly states 'Query DNS server logs' and 'Returns recent DNS queries and their responses', identifying the specific action and resource. This distinguishes it from sibling tools like dns_get_stats or dns_list_records.

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 clear context for when to use the tool (when querying DNS logs) and includes a prerequisite ('Requires the Query Logs app to be installed'). It does not explicitly mention alternatives or exclusions, but the context is sufficiently clear.

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