datacore_date

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

No annotations provided, so description carries full burden. Lists operations but does not disclose error behavior, return formats beyond 'today's date', auth needs, or limitations. Adequate but not comprehensive.

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 wasted words. First sentence is an imperative call to action; second sentence lists capabilities. Front-loaded and efficient.

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?

Missing details on return values for most operations (e.g., what does 'dow' return?). No output schema, so description should clarify; it only specifies 'today' returns date+dow. Incomplete for full usage.

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 coverage is 100% with descriptions. Description groups operations and provides context (e.g., 'parse relative expression like next monday'), adding moderate value beyond schema enum labels.

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 it's for canonical date operations, lists specific operations (today, dow, validate, add/sub, parse, org-stamp), and emphasizes replacing date-from-memory usage. Distinguishes well from siblings (capture, search, ingest, status).

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?

Explicitly instructs 'ALWAYS use this instead of typing dates from memory' and explains why (LLMs hallucinate). While no explicit when-not-to-use, context is clear and no sibling alternatives exist.

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