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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only states the output ('Upcoming deadlines with compliance probability %') and does not mention side effects, permissions, return format, or how the optional entity_id affects behavior. While it doesn't contradict any annotations, it offers minimal transparency into the tool's behavior.

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 a single concise sentence with no padding or redundant information. It is front-loaded with the core purpose, and every word earns its place. Though brief, it is appropriately sized for a tool with a single optional parameter.

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 absence of annotations and output schema, the description is too sparse to be complete. It does not explain the output structure, how the optional entity_id modifies results, or how 'compliance probability' is calculated. The tool is similar to several siblings, and the description lacks sufficient detail for an agent to confidently select and invoke it.

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's single optional parameter is fully described ('Optional for entity-specific probability'), and the tool description adds nothing beyond it. With 100% schema description coverage, the baseline score is 3; the description does not elevate this further.

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 clearly conveys the tool's output—upcoming deadlines with compliance probabilities—though it lacks an explicit verb like 'list' or 'get'. It distinguishes itself from sibling tools by focusing on deadlines and compliance percentage, which is unique among the list.

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 guidance is provided on when to use this tool versus alternatives such as early_warning or risk_forecast. The description gives no context, prerequisites, or exclusions, leaving the agent to guess the appropriate use case.

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