list_release_profiles

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

There are no annotations, so the description carries the full behavioral disclosure burden. The verb 'List' conveys a read-only operation and the description explains what objects are returned, but it does not mention response shape, ordering, or other behavioral details. This is acceptable for a simple zero-parameter list tool, but not richly transparent.

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 one concise sentence, front-loaded with the action and resource, followed by a brief clarifying appositive. Every word adds value and there is no filler or repetition.

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?

For a zero-parameter, no-output-schema list endpoint, the description is nearly complete: it names the operation, the resource, and the meaning of the resource. The only minor gap is not describing the shape of the returned list, but given the simplicity of the call signature, this is not a major omission.

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 tool has zero parameters and the schema is already complete with no properties. With 0 params, the baseline is 4; there is nothing for the description to add about parameter meanings, and it correctly avoids inventing parameter details.

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 opens with a specific verb and resource: 'List release profiles', so the action is unambiguous. It then defines what a release profile is ('required, ignored and preferred term rules applied to release titles'), which clearly distinguishes it from sibling tools like list_quality_profiles or list_delay_profiles.

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 implies when the tool is useful—when you want to see the term-rule profiles—but it does not explicitly state when to use it over alternatives or how it relates to create_release_profile/update_release_profile/delete_release_profile. There is no direct exclusion guidance, so the usage context is only implied.

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