get_list

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

With no annotations provided, the description carries full responsibility for disclosing behavior. It only states that the tool retrieves an existing list, which implies a read-only operation, but it does not mention any side effects, error conditions, authentication requirements, or how the password parameter is used. This leaves significant behavioral ambiguity for an agent.

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 states the verb, resource, and method in a direct manner. Every word contributes meaning, and there is no redundant or filler content.

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 simple nature of the tool (read by slug) and abundant schema coverage, the description is reasonably complete for basic usage. However, with no output schema and no annotations, it does not explain what the response looks like, what happens if the list is not found, or the role of the optional password in protecting the list, leaving some gaps for an agent.

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 provides 100% description coverage for both parameters (slug and password), so the schema fully documents what each parameter means. The description adds a minor clarification by saying "by its slug/URL identifier," reinforcing the slug parameter's purpose, but it adds no semantics beyond the schema. Baseline 3 applies.

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 uses a specific verb ("Retrieve") and resource ("existing task list") with a clear identifier method ("by slug/URL identifier"). This clearly distinguishes it from sibling tools like create_list (which creates) and generate_tasks (which generates), making the purpose unmistakable.

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 the tool is for fetching an existing list by slug, which is a clear usage context. However, it does not explicitly mention when to avoid using it or compare it with alternatives like create_list or generate_tasks. Since the context is clear but no exclusions or alternatives are named, it stops short of a 5.

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