list_logbook

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

Discloses key behavioral traits: tasks are limited to those completed within the last 'since_days' days (default 30) and ordered newest first. With no annotations provided, this covers the essential behavior, though the effect of the 'limit' parameter is omitted.

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?

Extremely concise with two clear sentences. The first sentence states the purpose, and the second provides key behavioral details. No superfluous information.

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 an output schema present, return values are covered. However, the description lacks documentation for the 'limit' parameter, and the term 'Logbook' might require implicit context. Overall, adequate but missing details on pagination or limit behavior.

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?

Adds meaning only for 'since_days' by explaining its role in filtering by completion date and its default value. The 'limit' parameter is not described at all. Since schema coverage is 0%, the description does not adequately compensate for the lack of parameter documentation.

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?

Clearly states the tool lists completed tasks from the Logbook, distinguishing it from siblings like list_all_tasks or list_today. The verb 'list' and resource 'completed tasks from the Logbook' are specific and unambiguous.

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?

Provides context that it shows completed tasks within a time window, but does not explicitly state when to use this tool versus alternatives like list_all_tasks or list_today. No exclusions or alternative tool names are given.

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