transport_cleanup

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

The description discloses mode-dependent behavior (hosted mode returns guidance, not cleanup) and that parameters are only for non-hosted mode (via schema). However, it lacks details on destructive scope, permissions required, or side effects beyond the schema, especially since no annotations are provided.

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 a single concise sentence that clearly conveys the tool's primary action and the hosted mode behavior. Every word earns its place, and it is appropriately front-loaded.

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 presence of an output schema, the description need not explain return values. It covers both modes and parameter applicability. However, it does not address edge cases like calling with parameters in hosted mode or prerequisites for cleanup, which would improve completeness.

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% with good descriptions. The description adds critical context by linking all parameters to 'Non-hosted only' mode, clarifying that they are ignored in hosted mode. This adds value beyond the schema alone.

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 action ('clean') and the resource ('non-hosted Transport state'), and distinguishes between non-hosted and hosted modes. However, it does not differentiate from sibling tools like transport_abort or transport_return, leaving room for ambiguity.

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 implies usage contexts (non-hosted vs hosted) but provides no explicit guidance on when to use this tool versus alternatives like transport_abort, transport_return, or transport_status. No exclusions or 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.