list_infrastructure_targets

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 disclosing behavior. 'List' implies a read-only operation, but the description does not mention pagination, account scoping, output format, or potential size/performance constraints. An agent gets no meaningful behavioral context beyond the verb.

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 indeed concise and front-loaded, with no wasted words. However, it is under-specified: nearly identical to the tool name and lacking any additional contextual structure that would help an agent use the tool correctly.

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?

With no annotations, no output schema, and only one short sentence, an agent cannot tell what an infrastructure target is, what the response looks like, whether results are limited, or how this listing relates to get_infrastructure_target. The information is minimally viable but clearly incomplete for correct invocation in an unkown context.

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 documentation coverage is 100%, so the account_id parameter is already documented as 'The account ID' in the schema. The description adds no extra meaning about how account_id is used, what scope it produces, or any relationship to other resources. Baseline 3 is appropriate because the schema does the heavy lifting.

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 states a specific action ('List') and resource ('infrastructure targets'), so an agent can tell this is a listing operation. However, it does not differentiate the tool from its sibling get_infrastructure_target beyond the plural/verb form, and the wording essentially restates the tool name.

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 given about when to use this tool versus alternatives such as get_infrastructure_target. There are no conditions, prerequisites, or exclusions, leaving the agent to infer the intended context from the name alone.

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