Overflow contents

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

Annotations already declare readOnly, idempotent, and openWorld, so the safety profile is covered. The description adds genuine non-obvious behavior: only action=offload data is present (drop patterns are NOT in S3; compact and tier_down route elsewhere) and it is sourced from a cap-CSV the MCP wrote. It stops short of disclosing any latency or pagination caveats, but the substantive scoping insight is a real value-add.

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?

Front-loads the resource definition before the routing guidance, with each sentence carrying distinct information (fields, filtering scope, usage framing, alternative). Slightly dense with parenthetical asides, but nothing is redundant.

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?

An output schema exists, so return values need no explanation. Combined with annotations covering the safety profile and a description that covers scope, filtering, and routing, an agent has everything needed to call this 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 coverage is 100%, so the schema already documents every parameter, including the limit truncation note and timeRange equivalences. The description reinforces the offload filter but adds no syntax or semantics beyond what the schema provides, so the baseline 3 applies.

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?

States a specific resource (offload S3 bucket contents) and enumerates the returned fields (per-pattern bytes, event count, time-first-seen, time-last-seen, growth rate). It also distinguishes itself from related siblings by naming log10x_retriever_query for rehydration, so an agent can route correctly without opening schemas.

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?

Explicitly frames the when: 'Call this as the maintenance-loop review: what's accumulating in my overflow queue?' and names the alternative (log10x_retriever_query) with the condition that selects it (incident or audit needs data back in the SIEM). Nothing is left to inference.

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