ansible-fetch-logs

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

With no annotations, the description must fully disclose behavioral traits. It states the tool fetches log files, but does not specify whether the operation is read-only, required permissions, or any limitations. Lacks depth for safe agent 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?

The description is well-structured with a clear 'Args' listing, and each sentence provides value without redundancy. It efficiently covers the parameters in a brief format.

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 tool has 8 parameters and a complex domain, the description covers the core functionality and parameters. However, it does not address prerequisites, output format (though output schema exists), or differentiation from similar tools like ansible-log-hunter.

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?

The description adds meaningful explanations for each parameter beyond the schema's titles and defaults (e.g., 'lines: Number of lines to fetch (like tail -n)', 'filter_pattern: Regex pattern to filter log lines'). This compensates for the lack of schema parameter descriptions.

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 fetches and analyzes log files from remote hosts, providing a specific verb and resource. However, it does not distinguish itself from the sibling tool 'ansible-log-hunter', which likely has a similar purpose.

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 alternatives (e.g., ansible-log-hunter), nor does it mention prerequisites or conditions for use. It only describes the tool's basic functionality.

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