browse_marketplace

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

With no annotations, the description carries full burden. It discloses what the tool returns (package IDs, names, categories, provider, versions, sizes, pricing) and lists categories and use cases. Missing details on pagination, rate limits, or result format (e.g., list), but adequate for a browse tool.

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?

Well-structured with sections (when to use, what you get, categories, examples, use cases). Concise enough, though slightly verbose. Information is front-loaded with purpose and usage guidelines.

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 and no output schema, the description provides thorough information about output contents and categories. Missing return type (e.g., list) and error handling, but sufficient for effective use.

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 100% as descriptions are provided for both parameters. The description adds context beyond schema: category filter and case-insensitive search, with examples. Provides meaningful guidance for parameter usage.

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 that the tool browses and searches available data packages in the SAP Datasphere marketplace, with specific verb 'browse and search' and resource 'data packages'. It distinguishes from siblings as no other sibling tool covers marketplace browsing.

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?

Explicit when-to-use scenarios are listed (e.g., 'User asks what packages are available'), including example queries and use cases. However, it does not mention when not to use or specific alternatives.

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