gotcha_create

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only says 'create a gotcha memory' without mentioning side effects, return values, permissions, or whether the operation is reversible. This is insufficient for a mutation 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?

The description is a single, concise sentence with no fluff, but it is too terse for the tool's complexity. It lacks structured detail (e.g., bullet points or examples) that would aid understanding without becoming verbose.

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 six parameters, no annotations, and no parameter descriptions, the description is grossly incomplete. It provides only a vague purpose and fails to explain the domain of 'gotcha', how it differs from other memory types, or what the expected output is. An agent cannot confidently call this tool correctly.

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 0%, and the description mentions none of the six parameters (title, statement, tags, details, project, trigger). The agent is left to infer parameter meanings from names alone, with no additional context from the description.

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 action (create) and resource (gotcha memory) and provides a defining attribute ('non-obvious behaviors'), which distinguishes it from siblings like bug_create or assumption_create. However, it doesn't elaborate on what a 'gotcha' specifically means in this context, leaving some ambiguity.

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?

There is no guidance on when to use gotcha_create versus its many siblings (e.g., bug_create, decision_create). The description implies usage for recording non-obvious behaviors but doesn't explicitly state conditions, alternatives, or exclusions.

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