vela_list_targets

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint, so the safety profile is clear. The description adds the API endpoint and clarifies that targets are cluster+namespace combinations, but does not elaborate on pagination behavior, response format, or other runtime characteristics.

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 concise with two short sentences. The first sentence defines the tool's purpose, and the second references the API. No wasted words; information is front-loaded.

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 list tool with pagination and filtering, the description is too sparse. It does not mention that results can be paginated (page, page_size) or filtered by project. While annotations cover safety, the description fails to give a complete picture of the tool's capabilities.

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 0% per context, yet the tool description makes no mention of parameters (page, page_size, project_name, response_format). The user must rely solely on the schema, which provides minimal description (only project_name has a brief Chinese description).

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 clearly states the tool lists delivery targets (cluster+namespace combinations) and provides the corresponding API endpoint. It distinguishes the tool from siblings like vela_list_project_targets by focusing on all targets, though it does not explicitly contrast them.

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 provided on when to use this tool versus alternatives (e.g., vela_list_project_targets). The description lacks context for appropriate usage scenarios or preconditions.

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