get_event_matrix

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

With no annotations provided, the description must carry the behavioral burden. It communicates that the tool returns a complete event matrix, implying a read-only reference lookup, but it does not describe the return format, whether the data is static, or any other behavioral details. This is adequate but minimal.

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 concise sentence that front-loads the tool's purpose and structure. Every word adds value, and there is no redundancy or filler.

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 reference tool with no output schema, the description is reasonably complete: it tells the agent what the matrix contains and how it is organized. It could go further by describing the exact return representation, but the core selection and invocation context is clear.

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 fully described with an empty properties object. There is nothing extra the description needs to add about parameters, so the baseline of 4 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 clearly identifies a specific resource: a complete BPMN 2.0 event matrix, and states the exact dimensions (start/intermediate/end x all triggers). This distinguishes it from sibling catalog tools like get_event_definitions_info or get_flow_elements_catalog because it explicitly presents the matrix structure.

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 gives no guidance on when to use this tool versus siblings such as get_event_definitions_info or get_bpmn_cheatsheet. There is no mention of alternatives, prerequisites, or situations where a different catalog would be more appropriate.

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