today_plan

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

No annotations are provided, so the description carries the full burden. It discloses that results are based on the local timezone of the process, which is a useful behavioral trait. However, it does not explicitly state that the tool is read-only, nor does it mention any side effects, permissions, or rate limits. The description is adequate but not rich.

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 very concise—two sentences that front-load the main purpose. No unnecessary words, and every sentence adds value.

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 the tool's simplicity, the description provides the core functionality. However, it lacks context on what 'scheduled' means (e.g., due date or something else) and does not describe the return format. With no output schema and many sibling tools, more detail would improve completeness.

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 0% schema description coverage, the description must explain parameters. It explains dayOffset with examples (1 for tomorrow, -1 for yesterday) and mentions filtering by workspaceId. This adds value beyond the schema. However, it does not specify the type or range of dayOffset, and workspaceId is only described as a filter without further detail.

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 returns cards scheduled for today. The verb 'Return' and resource 'cards scheduled for today' are specific. However, it does not differentiate from sibling tools like list_cards or search_cards, which might also return cards with date filters.

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 provides some usage context (e.g., using dayOffset for tomorrow/yesterday, filtering by workspaceId) but does not explain when to use this tool versus alternatives like list_cards or search_cards. No when-not-to-use guidance is given.

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