Log Analyzer MCP

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

Annotations already provide readOnlyHint=true and destructiveHint=false, indicating safe read operations. The description adds valuable behavioral context beyond annotations: it explains the polling mechanism, position tracking workflow, and the tool's purpose for 'polling-based log watching.' However, it doesn't mention rate limits, file access permissions, or what happens if the file is deleted/modified externally.

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 efficiently structured: purpose statement first, usage workflow second, parameter explanations third, return value fourth. Every sentence adds value with no redundancy. The parameter explanations use clear examples and practical guidance without unnecessary elaboration.

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's complexity (polling mechanism with position tracking), 6 parameters with 0% schema coverage, and no output schema, the description provides complete context. It explains the workflow, documents all parameters with examples, describes the return value, and distinguishes from sibling tools. The presence of an output schema would have reduced the burden, but the description adequately covers what's needed for proper tool invocation.

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?

With 0% schema description coverage, the description carries the full burden of parameter documentation. It provides detailed semantics for all 6 parameters: explains file_path purpose, clarifies from_position usage (0 for initial, previous position for subsequent), specifies max_lines range and default, shows level_filter format with examples, describes pattern_filter as regex, and lists response_format options. This fully compensates for the schema's lack of 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's purpose: 'Watch a log file for new entries since a given position' with specific verbs ('watch', 'returns', 'get') and resource ('log file'). It distinguishes from sibling tools like 'log_analyzer_tail' by emphasizing polling-based watching with position tracking rather than continuous streaming.

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 explicit usage guidelines: 'First call with from_position=0 returns the current end-of-file position. Subsequent calls with the returned position get new entries added since then.' This gives clear step-by-step instructions for when and how to use the tool, including the initial and follow-up call patterns.

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