tgtrack_new_api_token

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

Discloses critical behavioral trait: invalidates the previous API key. Also notes required confirm parameter being true. With no annotations, description carries full burden and provides strong transparency.

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?

Extremely concise: single sentence with warning emoji, action statement, and required condition. No extraneous text. Front-loaded with critical warning.

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?

Covers purpose, critical behavioral warning, and parameter requirement. Missing return value or success indicator, but no output schema exists. Mostly complete for a simple mutation tool.

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 0%, so description must add meaning. It specifies confirm:true as required, giving semantics for that parameter. chatID is implied to identify the channel, but no format or additional detail. Adds value but incomplete.

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?

Description states 'Create a new API key for channel' with a specific verb and resource. It distinguishes from sibling tools like tgtrack_create_integration or tgtrack_new_report_key by specifying channel API key. The warning about invalidation adds clarity.

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?

Description implies use requires confirmation (confirm:true) but does not explicitly state when to use vs alternatives or when not to use. No exclusion or alternative guidance provided.

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