Ops MCP Server

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

With no annotations, the description carries full burden and does well: it discloses the tool's purpose (directory listing), default values (prefix, bucket, max_items), and a critical behavioral constraint (must ask user for env if unspecified). It doesn't mention rate limits or auth needs, but covers core behavior adequately.

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?

Well-structured with a purpose statement, parameter details in bullet-like format, and a returns statement. Every sentence adds value, though the 'IMPORTANT' note could be integrated more smoothly. Slightly verbose but efficient overall.

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 4 parameters with 0% schema coverage and no annotations, the description provides complete context: purpose, parameter details with defaults and examples, usage rules, and output explanation. With an output schema present, it doesn't need to detail return values, making this comprehensive.

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 fully. It does: each parameter (prefix, bucket, max_items, env) is explained with semantics, defaults, examples (e.g., 'spark-logs/'), and usage guidance (e.g., 'Ask the user which environment'). This adds significant value beyond the bare 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 the specific action ('browse', 'navigate') and resource ('S3 log directory structure', 'folders to find logs'). It distinguishes from siblings like 'browse_s3' (general S3 browsing) and 'list_s3_recursive' (recursive listing) by focusing on log directories with navigation guidance.

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?

Explicit guidance is provided: 'Use the output to navigate deeper' explains iterative usage, and 'IMPORTANT: Do NOT guess or default. Ask the user which environment if not specified' gives clear when-to-use rules. It implicitly contrasts with 'browse_s3' by specifying log-focused browsing.

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