delimit_gov_run

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

With no annotations, the description carries full burden. Saying 'Run' implies mutation, but no information about side effects, idempotency, required permissions, or what happens to existing tasks. Minimal behavioral disclosure.

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?

Extremely brief (5 words), but conciseness sacrifices essential information. Overly terse for a tool with two undocumented parameters and ambiguous siblings.

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 an output schema, the description fails to convey the tool's core behavior, parameter roles, or when to invoke it. Inadequate for a tool with sibling ambiguity and no schema descriptions.

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%, and the description adds no meaning to task_id or repo. Without any parameter context, agents cannot infer their roles (e.g., which task, which repository).

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 states the verb 'Run' and resource 'governance task', indicating a Pro feature. However, it does not differentiate from sibling tools like delimit_gov_evaluate or delimit_gov_verify, leaving ambiguity about the exact scope.

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?

No guidance on when to use this tool versus alternatives (e.g., delimit_gov_new_task to create a task, delimit_gov_status to check status). Absent any context or exclusions.

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