get_overdue_tasks

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

The description does not disclose key behaviors such as default exclusion of completed tasks, pagination limits, ordering, or permission requirements. The 'pending' keyword is present, but the include_completed parameter suggests completed tasks can be included, which is not clarified. With no annotations, the description fails to fully convey behavior.

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 short (one sentence) and front-loaded with the core function. However, the '[query]' suffix detracts from clarity without adding 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 high number of parameters (11), absence of output schema, and many sibling tools, the description is insufficient. It lacks guidance on parameter usage, default behavior, and response format.

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%, so baseline is 3. The description adds minimal semantic value beyond the schema; the '[query]' tag is confusing as no 'query' parameter exists. It does not explain how parameters relate to the filtering logic.

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 retrieves overdue tasks with the phrase 'Muestra todas las tareas pendientes cuya fecha limite ya paso'. This distinguishes it from sibling tools like list_tasks (which likely lists all tasks) and get_agent_tasks. However, the trailing '[query]' is ambiguous.

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 is provided on when to use this tool versus alternatives among the many task-related siblings (e.g., list_tasks, get_agent_tasks). There is no mention of excluded contexts or conditions.

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