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

The annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered, and the description repeats 'Read-only' rather than adding to it. What it does add beyond the annotations is what an item looks like (id, customer, action, due time) and the fact that snoozed includes upcoming reminders. It says nothing about result-size limits or pagination, so it stops short of full disclosure.

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 short, front-loaded with the resource and its contents, then the parameters, then the workflow, with no filler sentences. It is dense and slightly list-like, but every clause carries information an agent can use.

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's account of the fields in each returned item is necessary and present. With two well-documented parameters and annotations covering the safety profile, nothing essential to selecting or invoking the tool is missing.

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% and both parameters already carry full enum and null semantics in the schema. The description mostly restates that view picks the list (default needs_you) and contactId limits to one customer, adding only the small clarification that snoozed also holds upcoming reminders, so the baseline of 3 fits.

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 gives a specific verb and resource ('List Needs you items, the to-do list SkipCalls keeps for the owner') and immediately expands on what an item contains (id, customer, what to do, due time). That is enough for an agent to tell it apart from get_work and update_work, which are explicitly named as follow-on steps.

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?

It says exactly when to use the tool ('answer "what needs me?"') and what to do next ('open one item with get_work and act or close it with update_work'), so the workflow is fully specified. The alternative lists are also distinguished by view, covering snoozed, waiting and done.

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