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

While annotations confirm it is read-only and safe, the description adds crucial contextual behavior by defining the meaning of the lists: 'Gaps are research work; stale active accounts are follow-up work; recent activity is context.' This helps the agent interpret the data types accurately.

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 definition is concise and structured like effective product copy. It immediately addresses the value proposition in the first sentence, followed by the core value and necessary internal definitions, ensuring zero wasted words.

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 lack of an output schema, the description provides a complete high-level overview of the results, detailing exactly which three types of information the user will receive and what those categories represent in a functional sense.

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?

Since the tool has zero parameters and 100% schema coverage, the baseline score of 3 is appropriate. The description adds no information regarding input parameters.

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 tool clearly defines its purpose as providing a daily, prioritized summary ('The CRM work queue'). It specifies the three main categories of output: open gaps, accounts going stale, and recent activity, making its function distinct from transactional siblings.

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?

The description explicitly answers 'when to use' by framing the tool's purpose around the question: 'what deserves attention today.' This establishes a clear use case for daily triage compared to more granular update tools.

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