close_repo_task

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

With no annotations, the description carries the full behavioral burden. It usefully discloses atomicity/transactionality and the set of side effects that occur. It does not say whether writes are reversible, what authorization is needed, what happens on partial failure, or what the response returns.

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 compact sentences; the core purpose ('transactional end-of-task writeback') is front-loaded and the list of effects follows efficiently. Dense but not bloated.

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?

For a 9-parameter mutation with no annotations and no output schema, the description covers the major side effects but not the parameter grammar or the relationship to the dry-run sibling. Workable for an experienced agent, incomplete for a new one.

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 0% across 9 parameters, so the description must compensate. It maps meaning onto several fields (gotchas, hotUpdate, taskLogEntry/progress, discoveries, escalations, rewrites), which is genuinely helpful, but leaves repo, project, agent_id and the array element shapes unexplained.

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?

States a specific purpose: an end-of-task writeback that performs several named effects (progress, hot memory, gotchas, discoveries/escalations, rewrites) atomically. It is more informative than a bare verb+resource, though it never explicitly distinguishes itself from the near-namesake sibling dry_run_close_repo_task.

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 phrase 'end-of-task writeback' implies the moment to call it, which is reasonable usage context. However, it names no alternatives or preconditions — nothing tells the agent when to prefer this over dry_run_close_repo_task or close_agent_task, both of which are siblings.

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