list_concerns

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

No annotations are provided, so the description must carry the full burden. It states the tool returns all concerns and lists included fields, which is useful. However, it gives no details on read-only status, pagination, ordering, or access requirements. Minimal but not misleading.

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?

A single sentence that is front-loaded with the core function ('All CART resource concerns') and immediately lists the key attributes. No filler or redundant information.

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?

Given the tool has no parameters and an output schema is present, the description fully explains what the tool returns. The only missing context is whether any authentication or special access is needed, but for a read-only listing tool this is often not required. It is adequate for the tool's simplicity.

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?

No parameters exist, so the baseline is 4. The description adds context about what each returned item includes (pipeline type, data source, etc.), which complements the empty schema.

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 all CART resource concerns and enumerates the attributes (pipeline type, data source, computability, docs). This distinguishes it from siblings like get_concern_details (single concern) and list_practices_for_concern (practices for a concern).

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 use when needing an overview of all concerns with their attributes. It doesn't explicitly name alternatives or exclusions, but the 'All' scope and the sibling tool names make the intended usage clear. For a simple list-all tool, this is sufficient context.

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