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

Annotations already declare readOnlyHint=true and destructiveHint=false. The description adds valuable behavioral context: it searches only owner-private items, only within a single workspace, and uses Typesense as the backend. It does not mention pagination or query limits, but the presence of an output schema reduces the need for return-format disclosure.

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 sentence with no filler. The verb and resource are front-loaded, and the qualifying constraints are packed efficiently without sacrificing clarity.

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 read-only search tool with an output schema, the description conveys the essential scope: authorized user, privacy level, workspace restriction, and search backend. It does not explain query syntax or pagination, but given the low complexity, existing schema descriptions, and read-only annotations, it is largely sufficient.

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 only 50%; the page and query parameters have no descriptions. The description implies query is the search text but provides no syntax or behavior details, and page is not mentioned at all. The workspace_id and workspace_name parameters are already explained in the schema, so the description adds little over structured fields.

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 ('Search'), names the resource ('Collect+ items'), and adds meaningful scope: the authenticated user's owner-private items within one workspace. This distinguishes it from siblings like list_collectplus_items and read_collectplus_item, which imply listing or reading without the search/query focus.

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 clearly implies when to use the tool: when searching the authenticated user's private Collect+ items in a workspace. However, it does not explicitly contrast with alternatives such as list_collectplus_items or search_notes, nor does it state when not to use it. The context is present but exclusions are absent.

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