tasks_get

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

With no annotations provided, the description carries the full burden of behavioral disclosure. 'List tasks' conveys a read-only collection operation and little else; it does not mention filtering, pagination, authentication, or any other behavioral traits.

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 concise at two words, but it is under-specified rather than efficiently complete. It earns its place as a minimal label, yet it does not provide enough structured meaning for a helpful tool definition.

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 tool with one optional parameter and no output schema, the description should at least mention the filtering capability and what the response represents. 'List tasks' leaves critical invocation context unexplained, so the definition is incomplete.

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 description coverage is 0% and the description does not mention the 'completed' parameter at all. The schema only reveals a boolean property, but the description adds no meaning about whether it filters tasks by completion status, leaving the agent to guess.

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 states a specific verb ('List') and resource ('tasks'), making the collection-level intent clear. It is not a tautology, though it does not explicitly differentiate from the sibling tasks_id_get beyond implying a list-versus-single distinction.

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?

There is no guidance on when to use this tool versus tasks_post, tasks_id_get, or tasks_id_delete. The description implies listing as opposed to creating, fetching, or deleting, but provides no explicit usage context, exclusions, or alternatives.

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