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

No annotations provided. The description reveals no behavioral details such as whether the list includes metadata, pagination limits, or ordering. It simply states the function without disclosing traits like read-only nature or potential performance characteristics.

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 description is a single, concise sentence that front-loads the key action and resource. Every word contributes meaning, with no filler or redundancy.

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?

Given no parameters and no output schema, the description adequately defines the tool's purpose. However, it could be improved by noting the return format (e.g., list of favorite objects) to provide complete context for an agent.

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?

With zero parameters and 100% schema coverage, the description adds meaning by clarifying that favorites are 'time-entry favorites (quick-entry shortcuts)', which helps an agent understand the domain context beyond the empty schema.

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 clearly states the tool lists the current user's saved time-entry favorites (quick-entry shortcuts). It specifies the resource type and user scope, distinguishing it from sibling tools like create_favorite or use_favorite.

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 usage for viewing all saved favorites but does not explicitly state when to use this tool versus siblings like use_favorite or create_favorite. No when-not or alternatives mentioned.

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