get_bpmn_cheatsheet

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

No annotations are provided, so the description carries the full burden of disclosing behavior. It only says the tool provides a cheat sheet, with no mention of output format, content coverage, side effects, or whether it reads static content vs. generates something. This is minimal behavioral disclosure.

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 extremely short, which is appropriate for a zero-parameter informational tool. However, it is a noun phrase rather than a complete sentence and adds no useful detail beyond the tool name, so it is not a top-tier concise description.

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?

Despite the simple zero-parameter interface, the description is not complete enough for an agent to know what a 'cheat sheet' will contain or how it relates to the many sibling educational/reference tools. No output schema exists, so the description should have explained the expected content or format.

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 schema coverage is 100%, so there are no parameter semantics for the description to clarify. Baseline 4 applies because there is nothing missing for an agent to provide as input.

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 identifies a specific resource — a complete BPMN 2.0 cheat sheet — and the tool name adds the 'get' action. It is clear about what artifact is returned, though it does not explicitly differentiate itself from other informational siblings such as explain_bpmn_concept or get_best_practices.

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?

There is no guidance about when to choose this cheat sheet over the many sibling reference tools (get_best_practices, get_validation_rules, catalogs, explain_bpmn_concept). An agent must infer use cases without any stated conditions or exclusions.

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