decision_getXmlByKey

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

Adds valuable versioning behavior ('latest version') not captured elsewhere. However, with no annotations provided, description carries full burden and omits safety profile (read-only vs destructive), error handling for missing keys, or auth requirements.

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?

Two efficiently constructed sentences: first defines operation, second states purpose. No redundant words or tautology. Front-loaded with specific technical details (DMN XML).

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?

Appropriate for a simple retrieval tool. Mentions return type ('DMN XML') compensating for missing output schema. Could improve by mentioning whether return is raw XML string or parsed structure, but adequate given scope.

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?

Zero parameters present; per rubric baseline is 4. Description mentions 'by key' which contextually implies how the resource is targeted, though actual key delivery mechanism (likely URL path) is outside schema scope.

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?

Excellent specificity: 'Retrieve' (verb) + 'DMN XML' (resource) + 'latest version...by key' (scope). Clearly distinguishes from sibling 'decision_getByKey' (likely returns metadata vs XML) and 'processDefinition_getXmlByKey' (different resource type).

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?

Provides clear context with 'Use to inspect the current decision table logic', explaining the inspection use case. However, lacks explicit contrast with 'decision_getByKey' or alternative approaches like retrieving specific versions vs latest.

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