ListTransports

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

The description includes '[read-only]' indicating no side effects, which is a key behavioral trait. It also mentions the types of requests returned. However, it does not disclose additional behaviors such as error handling, pagination, or results when no transports exist. The parameter 'modifiable_only' is described in the schema but not mentioned in the description.

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 brief and front-loaded with the '[read-only]' tag. It conveys the main purpose in a single sentence with no wasted words. However, it could be slightly more informative without losing conciseness.

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 no annotations, no output schema, and sibling tools like 'GetTransport', the description provides a basic understanding but lacks details on return value structure, error conditions, and usage context. It is minimally viable but leaves gaps for the agent.

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 descriptions cover both parameters (user and modifiable_only) with 100% coverage. The description does not add any additional meaning or context beyond what the schema already provides. Therefore, baseline 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 clearly states the verb 'list' and the resource 'transport requests', with scope 'for the current or specified user'. It specifies what type of requests are returned (modifiable and/or released). However, it does not explicitly differentiate from sibling tool 'GetTransport', which likely retrieves a single transport request.

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 explicit guidance on when to use this tool versus alternatives like 'GetTransport' or 'CreateTransport'. The description only mentions the scope (current or specified user) but does not provide when-to-use or when-not-to-use conditions.

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