list_bpmn_elements

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

With no annotations provided, the description carries the burden of behavioral disclosure. The verb 'Lista' implies a read-only operation with no side effects, which is useful, but the description does not mention return format, whether the list is static, or any limitations. This is minimally adequate but not rich.

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 a single sentence with no filler or redundant information. Every word contributes meaning, and the core action and object are 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 parameterless listing tool with no output schema, the description adequately communicates the return concept: all supported BPMN 2.0 elements. It could be stronger by naming the output shape or clarifying overlaps with sibling catalogs, but overall it is sufficiently complete for such a simple operation.

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 coverage is 100%, so there are no parameter semantics to document. The description adds value by clarifying the scope ('BPMN 2.0 soportados'), which is enough for a no-argument tool.

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 states a clear verb 'Lista' and a specific resource: 'todos los elementos BPMN 2.0 soportados.' It is easy to understand what the tool does. However, it does not distinguish itself from sibling catalog tools like get_flow_elements_catalog or get_activities_catalog, so the differentiation is left to the agent.

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 about when to use this tool versus the many sibling catalog and reference tools. An agent must infer that this is the general-purpose listing tool, which is not explicitly stated. There are no alternatives, exclusions, or contextual triggers mentioned.

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