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

Annotations already declare a safe, read-only, closed-world operation, so the safety profile is covered. The description adds genuine behavioral value by disclosing the detection logic: promises are cross-referenced against invoice on the job, follow-up job creation, payment receipt, or communication sent. It does not disclose return shape or limits, keeping it below 5.

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?

A single sentence, front-loaded with the verb and resource, with the most important scoping constraint ('ONLY unfulfilled') saved for the end. The parenthetical enumeration of checks is dense but earns its place by defining 'fulfilled'; slightly long for one sentence.

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?

There is no output schema, so the description carries the full burden of explaining return values; it conveys what is returned (unfulfilled promises) but not the record shape, pagination, or ordering. For a cross-referencing analytical query this leaves an agent with visible gaps.

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 0% and the single parameter 'days_back' is undocumented in both schema and description. The description hints at a time window via terms like 'next week' but never defines the parameter's unit, default, or the window it controls. For a conventional single numeric parameter this is the minimal viable level.

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 and resource ('Lists every tech note that says follow up...') and defines the exact scope of the result ('Shows ONLY the promises that were never fulfilled'). An agent can distinguish this from siblings like quotes_to_follow_up or overdue_tasks without inspecting schemas.

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?

Usage is implied by the result definition (a report of unfulfilled promises), but the description never says when to prefer this over close siblings such as quotes_to_follow_up, list_email_followups, or overdue_tasks. No exclusions or prerequisites are stated.

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