dotloop_get_pending_tasks

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

With no annotations provided, the description must disclose behavioral traits. It only states the action without clarifying whether the operation is read-only, what the return format includes (beyond the output schema), or any side effects. Minimal disclosure for a read operation, but insufficient detail for an agent to understand constraints like pagination or filtering.

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 a single sentence, which is concise but lacks structure. It conveys the core purpose without waste, but could benefit from additional detail (e.g., parameter hints) without becoming overly long. It is functional but minimal.

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 presence of multiple sibling tools for tasks (all, completed, pending) and an output schema, the description is insufficient. It does not differentiate usage scenarios, explain what constitutes a 'pending' task, or provide any additional context to help the agent decide when to use this tool versus alternatives.

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?

The input schema has 0% documentation coverage and the description does not explain the purpose or usage of 'loop_id' or 'profile_id'. An agent must infer their meaning from context, increasing the risk of incorrect invocation. The description adds no value beyond the schema's raw type and requirement status.

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 action ('Get'), the resource ('pending tasks'), and the scope ('in a Dotloop loop'). It distinguishes itself from sibling tools like dotloop_get_all_tasks_in_loop and dotloop_get_completed_tasks by specifying 'pending', making the purpose unambiguous.

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 no guidance on when to use this tool over alternatives such as dotloop_get_all_tasks_in_loop or dotloop_list_tasks. It does not explain the context of 'pending' or suggest any exclusion criteria, leaving the AI agent to infer usage without support.

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