timps_security_remediation

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

No annotations are provided, so the description carries the full behavioral burden. It discloses the intended deliverable—step-by-step patch plan, working code diff, and rollback—but does not clarify whether the tool modifies files, requires special permissions, or has side effects. This leaves meaningful ambiguity for an agent deciding whether invoking it is safe.

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, front-loaded sentence that conveys the input class, output artifacts, and purpose without any filler. Every word contributes useful information, making it highly efficient and easy to parse.

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 two-parameter tool with no output schema, the description covers the core input scenario and output expectations well. It could be slightly more complete by noting that 'request' is effectively required despite being marked optional in the schema, but overall the definition is adequate.

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 100%, and both parameters already have clear definitions in the input schema. The tool description adds no additional parameter-level context, so it meets the baseline for schema-heavy definitions but does not improve parameter understanding.

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 uses a specific verb ('Convert'), a clear resource ('a security finding'), and a precise deliverable ('step-by-step patch plan with a working code diff and rollback'). This clearly differentiates it from security-related siblings such as timps_security_guard or timps_incident_responder.

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 clearly implies the usage context: when a security finding needs to be converted into a remediation plan. It does not explicitly name alternative tools or exclusion criteria, but the input examples (CVE, SAST, secret, misconfig) provide sufficient contextual guidance for an agent.

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