Ops MCP Server

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It effectively describes key behaviors: it's a read operation (implied by 'list'), returns comprehensive data ('full recursive file listing with sizes, plus a summary'), has performance constraints ('max 2000' results), and includes important operational guidance about the 'env' parameter requiring explicit user input. It doesn't mention rate limits or authentication needs, but covers most critical aspects for this type of tool.

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 perfectly structured and concise. It starts with the core purpose, then usage guidelines, followed by detailed parameter explanations, and ends with return value information. Every sentence earns its place - there's no redundancy or wasted words. The use of sections (Args: and Returns) enhances readability without adding unnecessary length.

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 (6 parameters, recursive operation, filtering capabilities) and the presence of an output schema (which handles return value documentation), this description is complete. It covers purpose, usage scenarios, parameter semantics, behavioral constraints (max results), and operational guidance. The output schema existence means the description doesn't need to detail return format, allowing it to focus on the other critical aspects.

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 fully compensates by providing detailed semantic explanations for all 6 parameters. Each parameter gets clear purpose explanations, examples ('raw/hem_processing/', 'taxonomy', '.csv'), and important behavioral notes (case-insensitive matching, 'with or without dot' for extensions, default values, and the critical guidance for 'env'). This adds substantial 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 verb ('recursively list ALL files') and resource ('under an S3 bucket/prefix'), distinguishing it from siblings like 'browse_s3' (likely non-recursive) and 'list_s3_buckets' (lists buckets, not files). It explicitly mentions 'single call' to differentiate from paginated approaches.

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 scenarios: 'when the user asks to see everything in a bucket or folder end-to-end, wants a full file listing, or needs to find files by name or extension across nested folders.' It also includes a critical exclusion: 'IMPORTANT: Do NOT guess or default. Ask the user which environment if not specified.' This gives clear when-to-use and when-not-to-use guidance.

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