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

Annotations already declare readOnlyHint, idempotentHint and non-destructive, so the safety profile is covered. The description adds useful context beyond that: the content is grouped by section, and it hints the returned surface is interactive (tasks completed, records opened in Kepler) rather than a plain list. It does not flag the read-only nature explicitly, which would have resolved any ambiguity about the 'tasks can be completed' phrasing.

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 core action and its contents, then routes to the alternative, then notes argument optionality. The long parenthetical enumeration is dense but earns its place by telling the agent what the desk actually returns. No filler sentences.

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?

An output schema exists, so return-value detail is not required in the description. Combined with annotations covering the safety profile, the description is nearly complete for an opening/display tool; the only real gap is that 'scope' semantics (me vs workspace) are unexplained anywhere.

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 50%: 'days' carries a schema description with default and bounds, but 'scope' has only a bare me/workspace enum with no explanation of what workspace scope returns or when to choose it. The description adds only 'Both arguments are optional', which restates what the schema already shows (zero required params) and does not compensate for the undocumented scope semantics.

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 (opens the user's Kepler desk) and enumerates exactly what that surface contains: overdue/due-today tasks, submissions awaiting feedback, stale jobs, interviews missing feedback, today's agenda, grouped by section. This clearly distinguishes it from siblings like get_work_queue and get_activity.

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?

Gives concrete trigger phrasing ("open my desk", "show my day") and explicitly names the alternative for a different need: "For a text answer about what needs attention, use get_work_queue instead." When-to-use and when-to-use-something-else are both stated.

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