signavio_get_dictionary_categories

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

No annotations are provided, so the description carries full burden. It states 'Get all dictionary categories' but doesn't disclose behavioral traits like whether this is a read-only operation, if it requires authentication, pagination behavior, rate limits, or error conditions. The description is minimal and lacks essential context for safe invocation.

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 concise with just three words, front-loading the core purpose without any wasted text. It efficiently communicates the essential action, though this brevity comes at the cost of completeness.

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 no annotations and no output schema, the description is insufficient for a tool with 2 parameters. It doesn't explain what 'dictionary categories' are in this context, what format the results take, or any prerequisites. For a retrieval tool in a complex system like Signavio, more context is needed.

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 100%, with both parameters ('allCategories', 'showHidden') well-documented in the schema. The description adds no additional parameter information beyond what's in the schema, so it meets the baseline score of 3 for adequate coverage through structured data alone.

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 'Get all dictionary categories' clearly states the verb ('Get') and resource ('dictionary categories'), making the tool's purpose understandable. However, it doesn't differentiate from sibling tools like 'signavio_get_dictionary_category' (singular vs. plural), which could cause confusion about when to use each.

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 provides no guidance on when to use this tool versus alternatives. With siblings like 'signavio_get_dictionary_category' (singular) and 'signavio_search_dictionary', there's no indication of whether this tool is for bulk retrieval, filtering, or other specific use cases.

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