winston_request_logger

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

With no annotations, the description carries full behavioral burden, but it only states the creation intent. It doesn't disclose whether dependencies are modified, what artifacts are returned, whether files are written, or how the correlation ID is propagated — all relevant operational behavior for a code-generation tool.

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?

One tight sentence front-loads the verb, resource, and key differentiators. Every word is useful and there is no redundancy with the schema.

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 4-parameter tool with no annotations and no output schema, this description is thin. It omits Koa even though the schema allows it, doesn't explain what the tool returns, and leaves behavioral and usage questions unanswered.

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 description coverage is only 25%, so the description must compensate. It does add meaning by clarifying 'correlation IDs' maps to correlation_header and naming the frameworks from the enum, but it says nothing about include_body or api_key beyond what the schema already provides.

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 action ('Create'), a concrete deliverable ('request logging middleware'), and the implementation specifics ('using Winston with correlation IDs'). This clearly distinguishes it from sibling logging tools like pino_http_middleware and winston_logger_config.

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 implies a clear context: use this when you need Winston-based request logging middleware for Express/Fastify. It doesn't explicitly name alternatives or exclusion conditions, but the context is strong enough for an agent to route to it.

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