server_logs

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

Annotations indicate read-only, idempotent, non-destructive. Description adds requirements (SSH access), limitation (no follow), and clarifies actions. No contradiction.

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?

Description is well-structured with front-loaded purpose. Each sentence provides distinct info. Slightly verbose but appropriate for the complexity of actions and server modes.

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?

Covers all parameter defaults (lines 50, containers false), actions, server types, and limitations. Output schema is present, so return values are documented elsewhere. Comprehensive for a log/metrics tool.

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 5 parameters are described in schema (100% coverage). Description adds context: 'coolify' service only for Coolify servers, 'containers' only for monitor action. Adds value beyond 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?

Description clearly states it fetches logs and system metrics from Kastell-managed servers via SSH, with specific actions 'logs' and 'monitor'. It distinguishes between Coolify and bare servers, and has no sibling overlap for logs/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?

Provides guidance on when to use 'logs' vs 'monitor', notes live streaming not available via MCP, and explains service options for different server types. Lacks explicit mention of when not to use this tool vs alternatives, but siblings are distinct.

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