current_decision

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

No annotations provided, so description must disclose behaviors. Only states 'return' and 'live,' implying read-only, but no mention of side effects, permissions, error conditions, or uniqueness guarantees.

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?

Single 9-word sentence is concise and front-loaded. However, extreme brevity sacrifices clarity on parameters and usage.

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 having an output schema and 4 parameters, description omits return value context and parameter semantics. Complexity is high relative to the minimal description, leaving gaps for effective tool invocation.

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 0%, yet description gives no parameter details. It loosely mentions 'stable topic key' but doesn't explain 'repo,' 'scope,' or 'client.' Agents cannot infer correct usage from description.

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?

Description clearly states 'Return the one live decision for a stable topic key,' specifying verb, resource, and scope. It distinguishes from siblings like 'recall_decisions' (likely returns multiple) and 'record_decision' (create).

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?

Implies usage for stable topic keys, but no explicit when-to-use or when-not-to-use guidance. Lacks comparison to siblings like 'why' or 'decisions_as_of'.

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