goldhold_task_list

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

With no annotations provided, the description carries the full burden. The verb 'List' strongly implies a read-only operation, and 'open tasks' clarifies the filtering behavior. However, it does not disclose details like return format, ordering, pagination, or whether completed tasks are ever included, though the simplicity of the tool reduces the severity of those gaps.

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 concise sentence that front-loads the core action and resource. There is no filler or redundant information; every word contributes to understanding what the tool does.

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 — zero parameters, no required inputs, no output schema, and no nested objects — the description is complete enough for an agent to invoke it correctly. The phrase 'open tasks from the GoldHold task queue' provides sufficient context about what will be returned.

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 tool takes no parameters, so the schema fully covers parameter semantics and the description needs to add nothing further. The baseline score of 4 applies because there are zero parameters to document.

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 a specific resource ('open tasks from the GoldHold task queue'). It clearly differentiates this read-only listing operation from sibling task mutation tools like goldhold_task_create, goldhold_task_update, and goldhold_task_complete.

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 this tool is for retrieving open task queue entries, but it does not explicitly state when to choose it over alternatives or mention any exclusions. The usage context is reasonably clear from the phrase 'open tasks', but there is no direct comparison to sibling tools.

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