blueprint_get_terraform_configuration_sources

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

Annotations already declare readOnly, idempotent, non-destructive, open-world behavior, so the safety profile is covered. The description adds that results are paginated, which is useful, but says nothing about result visibility being project-scoped beyond what the schema states, nor about ordering effects of the anonymous apiVersion parameter.

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?

Two short sentences with the purpose front-loaded and no filler. The trailing raw HTTP path is marginally useful for API mapping and costs little.

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 output schema, the description should indicate what a returned configuration source contains or at least the pagination envelope; it only says 'paginated list'. Combined with fully documented parameters and read-only annotations, it is adequate but leaves the return shape underspecified.

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%: paging, sort, search, projects, and apiVersion are all documented in the schema, including the required projects filter. The description adds no parameter meaning beyond that, so the baseline 3 applies.

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?

States a specific verb and resource: returns a paginated list of configuration sources that serve as Terraform configuration storage. That is clear enough to distinguish it from most siblings, but it does not name the closely related blueprint_get_configuration_source_tree or blueprint_get_terraform_configuration_source_commit_list, which an agent must choose among.

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 gives no when-to-use guidance, no exclusions, and no indication of how to obtain the required projects IDs or why filtering is mandatory. An agent is left to infer that this is the enumeration step before fetching a tree or commit list.

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