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

Annotations already establish readOnly/non-destructive/closed-world, so the bar is lower, and the description still adds real behavioral context: results span personal space plus every workspace, the connection's workspace is ordered first, and open items are the default. It does not mention truncation behavior when limit is hit, which is the only notable gap.

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-loaded with the trigger phrasings, then the return shape, then the exclusion. The enumeration of query phrasings is long but each maps to a distinct user utterance, so it earns most of its space; a slightly tighter list would still read well.

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?

With no output schema, the description carries the return-value burden and does so: it says what items come back by default, what fields accompany each, and which scope wins for ordering. Combined with full schema coverage and annotations, nothing needed to invoke it correctly 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 coverage is 100% so the baseline is 3, but the description adds semantics the schema lacks, notably the result ordering ('the workspace this connection is in first') and the default result shape (open items with due date, labels, workspace). It reinforces rather than repeats the scope/default meanings.

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+resource (member's Connections to-do list) and enumerates the surface forms of the question it answers. It also names the sibling lane it is not (post_agent_todos_list), so an agent can separate it from the other to-do-adjacent tools without opening a schema.

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?

Explicit trigger conditions ('when the member asks what is on their to-do list... due or overdue... whether anything is waiting on them') plus an explicit instruction to answer only from this list, never chat history, and an explicit exclusion for the agent's own work log. Both when and when-not are covered.

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