transportDelete

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only states the action ('Deletes') without addressing critical aspects like permissions required, whether the deletion is reversible, side effects, error conditions, or what happens upon success. This is inadequate for a destructive operation.

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, direct sentence with no wasted words. It is front-loaded and efficiently conveys the core action, though it lacks depth, making it appropriately concise for its limited content.

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 destructive nature, lack of annotations, and no output schema, the description is incomplete. It fails to explain behavioral traits, usage context, or return values, leaving significant gaps for an agent to understand and use the tool safely and effectively.

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?

The input schema has 100% description coverage, with the parameter 'transportNumber' clearly documented. The description does not add any meaning beyond the schema, such as format examples or constraints, but the schema provides sufficient baseline information, justifying a score of 3.

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 'Deletes a transport' restates the tool name 'transportDelete' (tautology) without specifying what a 'transport' is or providing any distinguishing context. It uses a clear verb ('Deletes') but lacks resource specificity beyond the generic term 'transport', failing to differentiate from sibling tools like 'deleteObject' or 'createTransport'.

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?

No guidance is provided on when to use this tool versus alternatives. The description does not mention prerequisites, consequences, or related tools (e.g., 'transportRelease', 'transportInfo'), leaving the agent with no context for appropriate invocation.

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