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

The description adds behavioral context beyond the readOnlyHint and idempotentHint annotations by explaining that sponsored listings include paid rank and cumulative verified bid, while organic resources are unpaid external records with source provenance. This helps the agent interpret what kinds of results to expect, though it does not address pagination, filtering, or ordering behavior.

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 brief—two sentences—and front-loads the core action before explaining sponsored/organic semantics. It avoids unnecessary filler, though 'local inventory' is imprecise and could be clearer.

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 tool with 11 parameters, rich enums, and no property descriptions, this description is incomplete. It provides high-level result taxonomy and annotations cover read-only/idempotent behavior, but it leaves out how to select sources, paginate, filter by freshness, or interpret sort modes, which an agent needs to invoke the tool correctly.

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 0%, and the description does not explain any of the 11 parameters such as query, sort, source, freshness, cursor, organic_cursor, or min_success_rate. With low schema coverage and a high parameter count, the description was expected to compensate but fails to add meaningful parameter-level meaning.

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 a search action over inventory and distinguishes two result categories: sponsored listings with paid rank/verified bid and organic resources with provenance. This gives useful semantics that go beyond the title, although 'local inventory' is somewhat vague and does not explicitly mention agents.

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 this tool is for searching discovery results but gives no explicit guidance on when to choose it over sibling tools like get_discovery_sources, inspect_organic_resource, or compare_resources. No exclusions, prerequisites, or alternative conditions are provided.

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