finish_task

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

No annotations provided; description mentions proposing memories but does not clarify if the tool has side effects (e.g., auto-storing memories) or if it triggers the final response. Lacks disclosure of behavioral traits beyond the described actions.

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, front-loads the action. Second sentence is somewhat long but still efficient. No wasted words, though could be more structured for readability.

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 clear purpose, the description fails to document parameters and return behavior. For a tool with 6 parameters including nested objects, this leaves significant gaps for correct 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 has 6 parameters with 0% coverage in description. Description does not explain any parameter (e.g., cwd, outcome, testsRun, filesChanged, proposedMemories). The only hint is about memories in the description, but details are missing.

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 the tool's purpose: call before final response on non-trivial tasks, summarize work, and propose durable memories. It distinguishes from siblings like propose_memory by being specifically for task finalization.

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 explicit guidance on when to use (non-trivial tasks) and what to propose (decisions, root causes, etc.) and what to avoid (secrets, personal data). Does not explicitly state when not to use, but the context is clear.

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