cronos_leggi_todo

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

No annotations provided, but description discloses what is returned (markdown content, path, backup info) and implies read-only behavior; additional context about backup file adds transparency beyond basic function.

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?

Description is efficient with three sentences and a parameter list, front-loading the main action and delivering essential information without waste.

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 tool with one optional parameter and no output schema, description fully covers purpose, parameter, return values, and context (backup info), meeting completeness needs.

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 covers 100% of parameters with description already including format and optionality; description adds default behavior (oggi) and purpose, providing extra meaning beyond 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?

Description clearly states 'Legge il file todo.md di una data' with specific verb and resource, and distinguishes from siblings by focusing on reading a date-specific todo file, useful for answering 'che dovevo fare oggi?'

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 for when to use (reading today's or specific date's todo) and mentions related backup from cronos_prepara_domani, but lacks explicit exclusions or comparisons to alternatives.

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