decision_getByKey

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

No annotations provided, so description carries full disclosure burden. It compensates partially by listing return fields ('key, id, version, and deployment details'), but omits safety traits (read-only), error behaviors (404 scenarios), or whether this operation is idempotent.

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 sentences with zero waste: first states purpose and lookup method, second specifies return payload. Front-loaded with the action verb and appropriately scoped for a zero-parameter tool.

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?

Reasonably complete for a simple retrieval tool: compensates for missing output schema by documenting returned fields, and distinguishes itself from XML-fetching sibling. Minor gap: doesn't specify error response when key is not found.

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?

Input schema has 0 parameters (empty properties object), triggering the baseline score of 4 per evaluation rules. The description references 'by its key' which describes the retrieval mechanism rather than documenting a parameter, since no parameters exist in the schema.

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?

Specific verb 'Retrieve' + resource 'decision definition' + scope 'latest deployed version by key' clearly defines the operation. Effectively distinguishes from sibling `decision_getXmlByKey` (returns metadata vs XML) and `decision_list` (specific lookup vs enumeration).

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 implicit context that this fetches the 'latest deployed version' (not a specific historical version), but lacks explicit guidance on when to use this vs `decision_getXmlByKey` or error handling guidance if the key doesn't exist.

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