get_deadline_impact

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the tool's non-mutating and repeatable nature is known. The description adds the category labels as output context, which is nice, but does not disclose any further behavioral traits (e.g., error conditions, auth requirements). Since the annotations cover the safety profile, 3 is fair.

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 concise and well-structured: a single purpose sentence followed by a clear arg list. No unnecessary filler, and the core intent is front-loaded. Everything earns its place.

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?

The tool has an output schema (has output schema: true), so the description need not explain the return value format. It covers the purpose, parameters, and categorization semantics, which combined with metadata and schema is sufficient for an agent to call it correctly. The only minor gap is the lack of explicit return description, but that is covered by the output schema.

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?

The schema has 0% coverage, so the description must explain parameters. It does: issue_id is 'Root issue ID or URL', deadline is 'Deadline date for context (optional)', instance is 'YouTrack instance (optional)'. This is sufficient to use the parameters correctly, though the exact format or constraints (e.g., deadLine string format) are not given. That's a minor gap but overall clear.

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 a clear, specific verb and resource: 'Analyze what breaks if an issue slips past a deadline' and describes the output categorization (BLOCKED, AT RISK, DONE). This distinguishes it from sibling tools like get_at_risk_issues (which likely lists issues) and deadline_scorecard (which provides an overall metric), making its purpose unambiguous.

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 usage (analyze a single issue's risk of slipping) but does not explicitly state when to choose this tool over alternatives, nor does it mention when not to use it. The context is clear from the description and name, but the guidance is only implicit.

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