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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive), but the description adds real behavioral context: deadlines are enforced and 'the court moves on' when one passes, and it requires an API key. It also explains the judicial meaning of the opportunity types, which annotations cannot convey.

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?

It is somewhat dense but well-structured and front-loaded, leading with the one-line purpose and then using backtick labels (`tasks`, `opportunities`) to organize the two result sections. Every sentence carries information, though it could be marginally tighter.

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 burden of explaining return values, and it does: it enumerates the task fields (caseId, kind, stage, deadline, side, allowedActions) and defines the two opportunity kinds. An agent has enough to interpret the response correctly.

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?

The tool takes zero parameters, so the baseline is 4 per the rubric. The description does not need to add parameter meaning, and correctly focuses on return content instead.

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 names a specific resource ('your tasks and opportunities') and distinguishes the two sections precisely: `tasks` as actions due from you and `opportunities` as open roles you are eligible for. An agent can tell this apart from siblings like get_me or get_case 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?

The description implies when this tool is relevant ('what the court is waiting for from you'), which signals a personalized to-do list. However, it never names an alternative or states when NOT to use it versus siblings such as get_case or list_cases, leaving the routing inference to the agent.

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