deadline_scorecard

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

Discloses key behavioral traits: per-issue tracking, definition of 'missed_after_extension', strict vs. lenient approval counting, and exclusion of standups. No annotations to contradict.

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?

Well-structured with purpose upfront and bullet-pointed args, but somewhat lengthy. Could be slightly more concise.

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 6 parameters, no required, and presence of output schema, description covers the tool's purpose, usage, and parameter details adequately.

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?

With 0% schema coverage, description adds meaning for all 6 parameters: quarter format, user filter, projects, strict logic, exclude_standups, instance. Goes beyond schema.

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?

Clearly states it's a per-assignee deadline compliance rollup for a calendar quarter, with specific verb and resource. Distinguishes from sibling tools by focusing on compliance tracking.

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?

Provides clear context for when to use: tracking per-issue compliance, not cumulative. Includes parameter explanations but no explicit when-not-to-use or alternatives.

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