Overflow contents

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

Annotations already establish readOnly, idempotent, and openWorld behavior. The description adds valuable provenance: it is a customer-owned S3 bucket, the data is filtered by a cap-CSV the MCP wrote, and only action=offload patterns appear here. It does not discuss auth or rate limits, but it meaningfully extends what the annotations provide.

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 three tightly written sentences with no filler. It moves from return contents to filtering/routing, then to the maintenance-loop usage pattern and the downstream retriever_query alternative.

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?

With an output schema present and rich annotations, the description does not need to explain return values. It completely covers what the tool shows, when to call it, what it excludes, and where to go for raw events, leaving no material gap for an agent to call it correctly.

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 100%, so the schema already documents all five parameters, including the view const, limit behavior, service filter, timeRange enum, and environment. The description does not add syntax or format details beyond the schema, so the baseline of 3 is appropriate.

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 names a specific resource (customer-owned offload S3 bucket contents view) and enumerates exactly what it returns: per-pattern bytes, event count, first/last seen, and growth rate. It also distinguishes the tool from sibling data paths by noting that drop, compact, and tier_down patterns are not in this S3 overflow view.

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?

It explicitly frames the tool as the maintenance-loop review for 'what's accumulating in my overflow queue?' and routes the agent to log10x_retriever_query when offloaded events are needed for an incident or audit. It also states what is excluded and where those excluded actions route, giving 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.