Search service items

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

Annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=true and destructiveHint=false, so the safety and world-scope profile is fully covered structurally. The description adds no behavioral context beyond repeating that it is a keyword search — nothing about result cap, relevance ordering, or scope (workspace/user) behavior, which is relevant given the optional user_email and workspace_id parameters.

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 front-loaded sentence with no filler; efficient, though efficiency here reflects under-specification rather than disciplined editing.

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?

An output schema exists and all five parameters are documented in the schema, so the description needn't explain returns or arguments. What remains missing is the discriminating context — how this differs from list_service_items and what keyword matching actually does — leaving it only minimally viable for an agent choosing among catalog tools.

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 100% and each parameter carries its own description, so baseline is 3. The description only alludes to search_term ('by keyword') and adds no semantics about paging, workspace scoping, or act-as-user behavior beyond the schema.

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?

States a specific verb and resource: searching service catalog items, with the keyword-search qualifier. However, it does not distinguish itself from the sibling list_service_items or get_service_item, so an agent must infer which is which from names alone.

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?

No guidance on when to use this versus list_service_items (browse/list all) or get_service_item (fetch by id), and no mention of whether search_term supports partial matches, multi-word phrases, or boolean syntax.

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