list_tasks

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

No annotations are provided, so the description must bear the burden. It describes a read operation but does not disclose any behavioral traits beyond listing. The schema covers all parameters, but the description adds no extra context about side effects, authorization needs, or data limits.

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 efficient sentence that communicates the core purpose. It is appropriately sized for a simple tool, though it could be slightly expanded to include usage guidance without being verbose.

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 tool's simplicity, two fully documented parameters, and no output schema, the description provides sufficient information for an AI agent to understand the tool's function. It is complete enough for its straightforward use case.

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 100% description coverage for both parameters, so the description adds minimal value beyond the schema. It does not elaborate on parameter behavior or constraints beyond what is in the 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 the tool lists GoHighLevel tasks for a contact, specifying the resource (tasks) and context (for a contact). It effectively distinguishes from sibling list tools by mentioning 'for a contact' and the entity type 'tasks'.

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 implies usage context by stating 'for a contact', but it does not explicitly state when to use this tool versus alternatives like list_campaigns or list_events. No exclusionary conditions or prerequisites are provided.

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