list_myday

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

In the absence of annotations, the description carries the full burden. It only states the basic function, omitting key behavioral details such as whether completed tasks are included, if any ordering is applied, what happens on no results, or any authentication or rate-limiting requirements.

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?

Two sentences, no extraneous words. The first sentence clearly states purpose, the second adds parameter format and default. Every word serves a purpose.

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 list tool with one parameter and no output schema, the description is adequate but not fully complete. It lacks details on what 'scheduled' means in relation to 'My Day' (e.g., due date vs. manually added tasks), which could lead to misinterpretation given the tool name. Context about return values or pagination is also absent, though acceptable for simplicity.

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 single parameter 'date' has no schema description, but the tool description adds meaningful context: format YYYY-MM-DD and default behavior (today). This compensates well for the 0% schema coverage, helping the agent correctly format and invoke the tool.

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?

Description clearly states it lists tasks for a specific day, defaulting to today, with date format specified. The verb 'list' and resource 'tasks' are clear. However, it does not explicitly differentiate from sibling tools like list_schedule or list_goals; the tool name suggests 'My Day' concept but description uses 'scheduled', which might conflate with due dates.

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 guidance on when to use versus alternatives. Only implicit from context: default today indicates usage for current day tasks. No mention of exclusions or related tools, which is a gap given the many list-oriented sibling tools.

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