timps_technical_debt

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

No annotations are present, so the description carries the full disclosure burden. It mentions the output ('debt roadmap') but does not state whether the tool is read-only, requires git history or a local repo, has side effects, or what exactly the roadmap contains.

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?

A single dense sentence with no filler, front-loading the main action and method. Every phrase contributes meaning, and it is easily scannable.

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 an analysis tool with no output schema and no annotations, the description is sparse. It does not explain the format of the debt roadmap, prerequisites like git access, whether files are modified, or how to interpret results, leaving significant gaps for the agent.

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% for both parameters, so the baseline is 3. The description does not add parameter-specific details beyond what the schema already provides, but the schema itself sufficiently documents `request` and `language`.

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 'Quantify technical debt via radon complexity + git churn + TODO density; output a debt roadmap,' giving a specific verb, resource, and method. However, it does not differentiate from the near-identical sibling `timps_tech_debt_quantifier`, so it lacks explicit sibling distinction.

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?

No when-to-use context or alternatives are provided. The description implies it is for technical debt analysis, but there is no guidance on selecting it over the similarly named `timps_tech_debt_quantifier`, nor any exclusions, prerequisites, or scenario-based recommendations.

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