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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint=false, so safety is covered. The description adds behavioral detail about output composition: it includes the provision each matter runs under, flags items due within 7 days, and lists overdue open items separately within the same day window. It does not cover auth or rate limits, but that is not expected for this tool.

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?

Two dense sentences with no filler, front-loading the core action and scope. The second sentence handles the past-due edge case without disrupting the main flow.

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?

For a read-only listing tool with one optional parameter, no output schema, and full annotation coverage, the description is complete enough: it explains the window, default, flagging, provision detail, and separate past-due handling. Ordering, pagination, or result-count limits are omitted, but not essential here.

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 description coverage is 100%, so the 'days' parameter is already fully documented in the schema. The description restates the 1–90 range and default 30, and clarifies that the same number of days applies to the overdue window, but adds no syntax or format detail beyond the schema. Baseline 3 is appropriate.

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 specific verb ('Lists') and resource ('open deadlines in the institution's matters') with clear scope: due within the next N days, default 30, flagging items within 7 days, and separately listing recently passed deadlines. It does not distinguish itself from the sibling tool 'deadline_watch', so sibling differentiation is missing.

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 explicit when-to-use or when-not-to-use guidance is provided, and no alternative sibling tools are named. The agent can infer it is for checking upcoming deadlines, but there is no routing help against 'deadline_watch' or 'upcoming_hearings'.

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