audit_deadline_changes

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

Annotations already cover readOnly, openWorld, idempotent, and non-destructive behavior. The description adds valuable context by disclosing that the tool reads a local configuration file, '~/.yt-mcp/managers.json', for approver mapping. It also details the classification buckets, revealing how results are categorized. No contradiction with annotations, but it does not mention what happens if the config file is missing or malformed.

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 front-loaded with a concise purpose sentence, followed by a compact list of classification buckets and parameter documentation. Every sentence carries useful semantic weight, but the list of six classification categories adds length. It is still well-structured and without redundancy, warranting a high score.

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 the tool's complexity, the description covers inputs, defaults, a critical file dependency, and the high-level classification logic. Since an output schema exists, return shape is not required in the description. Missing failure-mode guidance (e.g., when managers.json is absent) and timezone/policy details prevent a perfect score, but overall it is largely complete for an agent to invoke 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?

The description includes an 'Args' section that explains every parameter in plain language, adding meaning the input schema titles and types fail to provide. For example, it defines 'projects' as 'Comma-separated project shortnames; empty = all accessible' and clarifies 'strict' as 'only keyword+date comments count as approval.' The defaults mentioned in the description align with the schema defaults, making parameter semantics crystal 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?

Description opens with a clear verb+resource: 'Audit Due-Date shifts in a period; classify each as compliant/unauthorized.' It also lists specific classification buckets, which distinguishes it from generic 'audit_issue_list' or 'get_deadline_impact'. However, it does not explicitly mention what distinguishes it from sibling tools such as 'audit_issue_list', so the agent must infer the distinction from context.

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 provides no guidance on when to choose this tool over alternatives. It lacks explicit when-to-use or when-not-to-use statements, and no sibling tools are referenced for comparison. The intended usage is implied by the purpose statement, but the tool selection guidance is essentially absent.

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