search_assets

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

Annotations already declare readOnlyHint=true, openWorldHint=true, and destructiveHint=false, so the tool's side-effect profile is covered. The description does not contradict these annotations and adds no misleading behavioral claims.

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 short, front-loaded with the core purpose, and uses a clean two-line format for parameter notes. There is no redundant or irrelevant text.

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 core search behavior is clear, and an output schema exists, so return values need no explanation. However, the relationship between workspace_id and hub_profile_id is not clarified, and the valid values for types/exclude_* are not specified, leaving some contextual gaps for a 7-parameter tool.

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 description covers workspace_id and types with practical guidance, but leaves hub_profile_id, search, and the three exclude_* parameters unexplained beyond their names. The schema provides no descriptions, so the description only partially compensates for the low schema coverage.

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 operation ('Search'), the resource ('assets'), and the scope ('in a hub profile by keyword'). It distinguishes itself from siblings like list_assets and search_contents by explicitly focusing on keyword-based asset search.

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 provides useful guidance for workspace_id (how to obtain it) and types (with an example), but does not explicitly explain when to prefer this tool over alternatives like list_assets or search_contents. It also does not mention the exclude_* parameters, which may require clarification for full usage.

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