sd_get_diary_entry

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

With no annotations, the description carries the burden. It adds valuable context about available years (1808-1811, 1817, 1820-1834) and missing years, plus the return structure (date, left/right content, raw XML). It doesn't mention behavior for invalid dates, but the limitations are well documented for a read-only retrieval.

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 well-organized into PURPOSE, WHEN TO USE, WHEN NOT TO USE, Args, and Returns. Each section is concise and purposeful without redundancy, making it easy to parse and act upon.

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 single-parameter tool with an output schema, the description covers all necessary context: purpose, usage, exclusions, parameter format, and return structure. It is complete and self-sufficient for an agent to invoke correctly.

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 0% for the date parameter, and the description fully compensates by specifying 'Date in ISO 8601 format (YYYY-MM-DD)' with an example. It also documents the ctx parameter, adding meaning beyond the bare 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 'Retrieve a specific diary entry by date' and further explains 'Access a specific day's entry from Schleiermacher's diary'. It distinguishes itself from sibling sd_get_diary_entries (plural) by explicitly noting this is for a specific date, not a range.

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 explicit WHEN TO USE cases (specific date, after search) and WHEN NOT TO USE cases, naming alternatives: 'use get_diary_entries()' for date ranges and 'use search_in_documents()' for keyword search. This gives clear decision guidance.

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