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

The readOnlyHint/openWorldHint annotations already establish the safety profile, so the description's job is to add operational context. It does add useful detail about what is returned, including the semantic meaning of the primary flag ('the one SDKs receive') and why the structure summary exists, but it says nothing about result ordering, whether results are capped, or behavior on an invalid project/environment.

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?

It is front-loaded with purpose and return contents, and every clause is functional. The final two sentences about search duplicate what the schema already says, which is the only wasted space.

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 carries the burden of describing return values, and it does so thoroughly, including the primary flag and the structure summary fields. The remaining gaps (ordering, result caps, error behavior) are minor for a simple read-only list tool.

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 description coverage is 100%, so all three parameters are already documented, including that search is a case-insensitive substring match and that list_projects discovers valid ids. The description's sentence about search restates the schema almost verbatim and adds no new semantics, so the baseline of 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?

The description gives a specific verb and resource ('List the remote configurations') and scopes it to 'the current project and environment', then enumerates exactly what each row contains (id, name, alias, primary flag, structure summary). It implicitly distinguishes itself from get_configuration by framing the result as a way to 'decide which config to read ... before requesting content', but it never distinguishes itself from the sibling search_configuration, and its 'Use search' phrasing refers to a parameter in a way that could be misread as naming that sibling tool.

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?

There is clear when-to-use guidance: call this to survey configurations and gauge size before requesting content with get_configuration. It also explains the search parameter's optionality ('Omit it to get all configurations'). It stops short of stating when to prefer search_configuration over this tool, which is the one routing decision an agent still has to guess.

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