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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds the 'authenticated user's owner-private' scope, which is useful context, but does not disclose pagination, ordering, or workspace selection behavior beyond the schema.

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?

A single sentence that front-loads the action, resource, and scope. Every word earns its place; no redundancy or filler.

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 output schema covers return values, and read-only annotations reduce the need for safety disclosure. However, pagination behavior and the meaning of 'owner-private' in multi-workspace contexts are not explained, and filter parameters like type and limit lack semantic detail.

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 coverage is 40%, with workspace_id and workspace_name described but page, type, and limit only having types/enums. The description adds no new meaning for these parameters. Baseline 3 applies because the uncovered parameters are somewhat self-explanatory from their names.

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 ('List') and resource ('authenticated user's owner-private Collect+ items') and scopes it to 'one workspace.' This is clear, but among many sibling list tools, the qualifier 'owner-private Collect+ items' only partially differentiates it from search_collectplus_items and read_collectplus_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: use this when the agent needs to list owner-private Collect+ items in a workspace. It does not explicitly state when not to use it or name alternatives such as search_collectplus_items. Schema notes about default workspace are helpful but not usage guidance.

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