catalog_discover

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

Annotations already signal read-only and closed-world behavior; the description adds that results are gated by enabled PluginBinding and that context controls scope matching. It does not contradict the annotations, and it surfaces the non-obvious PluginBinding dependency.

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, and the main action ('returns bounded candidates') is placed near the front. It is concise but slightly cryptic; some structure or examples would improve comprehension.

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?

With five parameters, one of which accepts arbitrary object properties, and no parameter descriptions, this short description is insufficient for an agent to construct a correct call. The output schema may define the result shape, but invocation semantics such as query filtering, pagination via cursor/limit, and the expected shape of context are missing.

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%, so the description needed to document the five parameters, but only context (and indirectly PluginBinding) is addressed. limit, query, scope, and cursor receive no semantic explanation.

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 states a specific behavior: returning bounded candidates based on enabled PluginBinding, and assigns context a role in matching scope. This goes beyond the tool name, but it lacks a plain-language definition and does not distinguish catalog_discover from siblings such as catalog_list or catalog_effective.

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 is given about when to use this tool instead of catalog_graph, catalog_list, or catalog_effective, and no exclusions or prerequisites are stated. The only usage hint is that context determines matching scope, which is implicit rather than explicit direction.

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