implement_feature_web

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It mentions a '7-step workflow' (Types, Service, Hooks, Components, Screens, Routes) which gives some flow transparency, but it doesn't disclose side effects: whether this mutates code, creates files, requires commit permissions, modifies the git history, or what the impact is on the existing codebase. For a mutating implementation tool with zero annotation coverage, this is a significant gap.

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 description is compact — two sentences. The first sentence explains the workflow steps concisely, the second gives a strong usage directive. No wasted words, though it could be improved by front-loading the core action even more explicitly.

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 tool that appears to perform substantial code generation and file modification, the description is minimal given the tool's complexity. There's no output schema so the description should explain what a successful implementation produces (files created, patterns followed), and there's no mention of failure modes or rollback behavior. The 7-step workflow naming is helpful but doesn't cover post-execution state or what the agent should verify after calling.

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 100% with a single parameter 'ticket' described as 'Ticket description'. The description adds workflow context (how the ticket flows through the 7 steps) which is beneficial. However, the description doesn't add syntax or format specifics for the ticket beyond what the schema provides — the schema already describes it as a 'Ticket description' string. The value-add here is the workflow context rather than parameter details.

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 it executes a Next.js feature implementation workflow and names the 7-step process, giving clear verb+resource. However, it does not distinguish itself from the sibling 'implement_feature' tool, which appears to be the general-purpose version without the '_web' suffix. The purpose is clear about what it does but ambiguous about how it differs from its sibling.

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 says 'ALWAYS use this for Next.js features' which provides a strong usage directive and implies this is the canonical tool for the platform. However, it doesn't explicitly state when NOT to use it or name alternatives (like when to use implement_feature_mobile or the base implement_feature), leaving the exclusion boundaries implicit.

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