get_collection_items

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

No annotations are provided, so the description must bear full burden. It states 'Get items' indicating a read operation, but offers no details on permissions, rate limits, side effects, or return format beyond a generic 'Items in the collection'. Given the output schema exists, more behavioral context would be helpful.

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 extremely concise with clear sections (Args, Returns). Every sentence provides necessary information without redundancy or fluff.

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?

The tool has 2 parameters and an output schema. The description explains both parameters with example values (e.g., 'root') and indicates what is returned. It is complete for a retrieval tool, though it could optionally mention the integer type for collection_id explicitly.

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?

Schema description coverage is 0%, but the description adds meaningful explanations: 'collection_id' is described as 'use "root" for root collection' and 'item_type' lists valid values ('all', 'dashboard', 'card', 'collection'). This compensates for the schema's lack of descriptions.

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 'Get items (dashboards, cards, collections) in a collection.' This specifies the verb 'get' and the resource 'items in a collection', distinguishing it from sibling tools like 'list_collections' (only collections) or 'get_card' (single item).

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 by listing parameters, but does not explicitly state when to use this tool versus siblings like 'list_collections' or 'get_dashboard_cards'. No when-not-to-use or alternative suggestions are provided.

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