Get List

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. The word 'Get' implies a read operation, and the phrase 'and its cards' clarifies the response scope. However, it does not mention authentication requirements, potential errors, or any additional behavioral details such as whether the response is nested or includes card fields. It is minimally adequate but not rich.

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?

One sentence with no filler. The core action, resource, and parameter are front-loaded, and every word contributes to the meaning. It is as concise as possible while remaining informative.

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 simple one-parameter read tool, the description covers the essential elements: what the tool does, what it returns, and the input needed. It lacks explicit usage guidance and behavioral caveats, but given the low complexity and rich sibling context (which an agent can infer from), it is nearly complete. A brief note on when to choose this over get_board_lists would make it fully complete.

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 schema coverage is 100%, and the single parameter is documented as 'The ID of the list' in the schema itself. The description repeats the parameter's role without adding extra semantic detail such as the expected format (e.g., Trello's short or full ID), so it does not add value beyond the schema baseline.

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 ('Get'), a clear resource ('a Trello list and its cards'), and the identifying parameter ('by list ID'). This clearly distinguishes it from sibling tools like get_board_lists (which retrieves multiple lists per board) and get_card (which retrieves a single card). The scope is unambiguous.

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 gives no guidance on when to use this tool versus alternatives. It does not mention that this tool is for retrieving a specific list by ID as opposed to listing all lists on a board, nor does it point to any sibling tools. The usage context is only implied, not stated.

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