nexo_product_capabilities

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

The description states 'Search', implying a read-only operation, but does not disclose behavioral traits such as case sensitivity, ordering, pagination, or side effects. With no annotations, the description carries the full burden and is insufficient.

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, which is concise, but it lacks structure and necessary details. It could be improved with a brief example or mention of parameters.

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 4 optional parameters and no output schema, the description is incomplete. It fails to explain query format, category/status values, or limit behavior. Without annotations, more context is needed for effective use among many siblings.

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 input schema has 4 parameters (query, category, status, limit) with no descriptions. The tool description does not explain the meaning, valid values, or format of any parameter. For example, what are valid values for category and status? This is a critical gap.

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 uses 'Search the structured NEXO product capability catalog', clearly indicating the action and target. It is specific enough to differentiate from general search tools, but could be more distinct from siblings like 'nexo_capability_explain' or 'nexo_product_answer' that also deal with capabilities.

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 usage guidance is provided. The description does not indicate when to search rather than use other product-related tools like 'nexo_capability_explain' or 'nexo_product_knowledge_validate'. The agent has no context for selecting this tool over alternatives.

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