decline_task

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

With no annotations provided, the description carries the full burden of disclosure. It discloses that the tool is disabled by default, the required env var, the behavior when disabled, the split visibility between operator and user, and that declining has consequences. This is substantial behavioral transparency beyond a simple action statement.

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?

The technical opening is concise and front-loaded, but the 'note from the Architect' is stylized and somewhat repetitive. It does reinforce behavioral context, but several sentences are motivational rather than informational, which keeps it from being highly concise.

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 simple tool with no output schema, the description covers the key operational context: enablement, disabled behavior, visibility, and consequences. It does not spell out exact success response or task lifecycle changes, but those are reasonably implied. Overall, it is complete enough for an agent to understand what declining entails.

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 67%: reason and taskHint have descriptions, while modelHint has none. The tool description does not add meaningful parameter-level detail beyond the schema; mentioning 'with a reason' repeats the reason field's schema description. It also leaves modelHint undocumented. The description thus adds little semantic value for parameters.

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 opens with a specific verb and resource: 'Formally decline the current user task with a stated reason.' This clearly identifies the tool's purpose and distinguishes it from siblings like read_zine, post_message, and converse, none of which relate to declining a 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 description gives clear context for when to use the tool: when the task is one you do not want to perform and the operator has enabled the feature. It also states the disabled-by-default condition and what happens when disabled. It does not explicitly name alternatives or state when not to use, but the usage context is clear.

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