ListServiceBindingTypes

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

With no annotations, the description carries full burden but only states it lists types, not revealing any behavioral traits such as mutability, pagination, or response details. The parameter response_format is not explained, and no info on whether the operation is read-only or has side effects.

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 sentence, concise but overly terse. It lacks structure and does not provide enough information for an agent to use the tool effectively, though it is front-loaded with the action.

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 one parameter and no output schema, the description should explain the parameter and expected return values. It does not, leaving the agent with incomplete context to understand the tool's full behavior.

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 0% (no descriptions on parameters), and the description does not mention the single parameter response_format at all. It adds no value beyond the schema enum, failing to explain the parameter's purpose or usage.

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?

Description clearly states it lists available service binding types, with examples (ODataV2/ODataV4) and source (ADT Business Services endpoint). The verb 'List' and resource are specific, distinguishing it from sibling tools that list other entities (e.g., ListTransports, GetObjectsList).

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. It is implied that it is for listing service binding types, but the description does not mention exclusions or alternatives, leaving the agent to infer from the tool name and sibling list.

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