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

Annotations already confirm read-only, non-destructive, and closed-world behavior, so the description doesn't need to restate safety. It adds useful behavioral context by specifying the returned shape: one row per project/task with daily minutes and daily/weekly totals, which is not in annotations or an output schema. It does not cover pagination or empty-state behavior, but for a simple read that is minor.

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?

A single well-formed sentence that front-loads the main purpose and then enumerates the return structure. No 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?

For a simple read-only tool with annotations and full parameter documentation, the description covers what is needed: scope, grouping, and totals. With no output schema, explaining the return rows and totals fills the main gap.

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 the single parameter ('day') is fully documented there with format and default. The description adds no additional meaning about the parameter, so the baseline 3 applies.

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?

Specific verb ('Returns') and resource ('user's own timesheet'), with explicit scope ('one week, Monday to Sunday') and return structure. The phrasing 'user's own' and 'week' differentiates it from siblings such as get_time_report or list_time_entries without needing to name them.

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?

No explicit when-to-use, alternatives, or exclusions are given. Usage is implied by the scope ('one week, Monday to Sunday'), but the agent must infer that this is for a personal weekly view rather than project/task time reports.

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