uodo_get_decision

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

No annotations provided, so description carries full burden. It discloses a side effect (saving .md archive in local mode) but does not clarify read-only nature, permissions, or other behaviors beyond the basic fetch operation.

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 two sentences, front-loaded with the primary purpose, and efficiently conveys key information without unnecessary words. Slightly more brevity could be achieved, but it remains effective.

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 the tool's simplicity (1 param, no output schema, no annotations), the description covers the return content (metadata, sentence, justification) and the local file behavior, making it sufficiently complete for an agent to understand input and output.

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 coverage is 100% for the single parameter 'id', and the description merely repeats the schema's context ('ID decyzji z wyników uodo_search_decisions'), adding no additional meaning or syntax details beyond what the schema already provides.

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 states the tool fetches a full decision by ID, including metadata, sentence, and justification, and distinguishes it from sibling tools (uodo_search_decisions, uodo_list_search_fields) by focusing on retrieval of a single detailed item.

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 implies usage when you have a decision ID from uodo_search_decisions but lacks explicit guidance on when not to use it or alternatives. Siblings are listed but no direct comparison or exclusion criteria.

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