list_items

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

With no annotations, the description carries the full burden and does state the core read-only behavior and optional filters. However, it does not disclose pagination semantics, default result sizes, return shape, or how the workspace parameter affects results, leaving the agent with only minimal transparency.

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, front-loaded sentence with no filler or unnecessary wording. It is appropriately concise, though it sacrifices some useful context that would be needed for a higher completeness score.

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 no annotations, no output schema, five parameters, and many list_* siblings, the description is too thin for reliable selection and invocation. It does not explain what 'items' includes, how list_items relates to the specialized list tools, or how workspace selection works.

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 has 0% description coverage, so the description must compensate. It only clarifies 'type' and 'search term,' leaving 'top,' 'skip,' and 'workspace' unexplained; it also does not specify valid values for 'type.' This is only partial coverage of the five parameters.

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 verb 'List' and the resource 'workspace items,' and it mentions optional filtering by type or search term. However, it does not explicitly distinguish this generic tool from the many sibling list_* tools like list_reports or list_tables, so it stops short of full clarity.

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 list_items versus the numerous specific list_* sibling tools. There are no exclusions, prerequisites, or hints about which scenarios call for the generic tool instead of a specialized one.

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