delimit_agent_complete

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

No behavioral details beyond the completion action. Annotations are absent, so description carries full burden, but it doesn't mention idempotency, side effects, or auth requirements. Minimal transparency.

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 sentence is brief but effectively communicates core purpose. Could benefit from slightly more detail without losing conciseness.

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 3 parameters and no annotations or output schema description, the description is incomplete. Does not explain return values or success/failure indicators. Lacks essential context.

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 3 parameters with 0% description coverage. The description adds no meaning to 'task_id', 'result', or 'files_changed'. Baseline is 1 as description fails to compensate.

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 verb 'Mark' and resource 'agent task', and specifies the action 'as complete'. It distinguishes from siblings like delimit_agent_check and delimit_agent_status by indicating this is the completion action.

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 includes '(Pro)' hinting at user tier, but provides no guidance on when to use this tool versus alternatives like delimit_agent_dispatch or delimit_agent_handoff. No when-not-to-use instructions.

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