clikta_list_tools

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

No annotations are provided, so the description must convey safety and behavior. It indicates a read-only listing operation ('List'), but does not discuss return format, pagination, or error cases. For a simple list tool, this is adequate but leaves room for more transparency about what the agent can expect.

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 that front-loads the action and resource, then adds a purpose clause. Every word is useful, avoiding redundancy while conveying the tool's purpose and context.

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 zero parameters and no output schema, the description is quite complete: it explains the tool's role within the recording workflow and the rationale for using it. It could be slightly more explicit about the return value (e.g., that it returns a list of tool IDs), but the purpose clause implies this, making the description strong for a simple list tool.

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 has zero parameters, so the schema provides full coverage with no missing documentation. The description adds value by explaining the purpose of the list (obtaining a toolId to avoid duplicates), which helps the agent interpret the output. This meets the baseline for zero-parameter tools.

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's function: 'List the products/tools already registered in the Clikta workspace' with an example ('Acme Dashboard'). It distinguishes itself from sibling tools by emphasizing that this list is used to attach a new recording via toolId, avoiding duplicates.

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 a concrete usage scenario: when you need to attach a new recording to an existing tool, list the registered tools to get a toolId. While it doesn't explicitly mention alternatives, the purpose clause clarifies when this tool is appropriate, and the sibling list shows it is not for listing recordings.

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