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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint=false, and destructiveHint=false. Beyond this, the description discloses the output behavior — sorted by due date, flagged when due within 7 or 14 days — and the batch cap of 50. Does not mention error behavior for invalid event/date combinations, but adds meaningful behavioral context.

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?

Front-loads purpose, then scope, then output behavior, then usage. The middle sentence listing legal regimes is dense but relevant. Overall appropriately sized for a tool with a moderate-sized schema, with only mild redundancy around the regimes mentioned in both description and schema.

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 read-only annotations, a fully documented schema, no output schema, and the description's disclosure of sort order and due-date flagging, an agent has enough to invoke correctly. Lacks explicit mention of the return shape per account (e.g. fields in each result), which is the only minor gap.

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%, including detailed per-event documentation in the enum, so the baseline is 3. The description reinforces the 'from an event and its date' pairing and the 50-account cap but does not add semantics the schema doesn't already provide.

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?

States a specific verb and resource ('Computes the due date of a statutory period for each of up to 50 recovery accounts') and enumerates the legal regimes covered (SARFAESI, DRAT, NI Act). Distinguishes itself from siblings like sarfaesi_timeline and panel_deadline_tracker by virtue of the multi-account batch scope.

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 ('Use to build or check a deadline list across several accounts') but does not name explicit alternatives or exclusions relative to sarfaesi_timeline, which appears to be a closely related sibling. Gives intended use without a when-not-to-use clause.

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