nexo_capability_explain

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

With no annotations, the description must fully disclose behavior. It only mentions 'with source and safety context,' hinting at output content but not revealing side effects, read-only nature, or required permissions. The tool likely reads data but that's not confirmed.

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 short sentence (11 words), which is concise but sacrifices necessary detail. It front-loads 'explain' but lacks structure for multiple dimensions.

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 output schema, no annotations, and 0% schema coverage, the description fails to cover essential aspects like return value, parameter usage, or constraints. It is severely incomplete for a tool with three parameters.

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 0% and the description contains no information about the three parameters (capability_id, query, locale). The agent has no guidance on how to populate them, making selection and invocation guesswork.

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 'Explain one NEXO product capability with source and safety context' clearly states a specific verb (explain) and resource (one NEXO product capability), and adds unique context about source and safety. However, it doesn't explicitly differentiate from sibling 'nexo_product_capabilities' which lists capabilities, but the 'one' suggests a single explain action.

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 on when to use this tool versus alternatives like nexo_product_capabilities or nexo_tool_explain. There is no indication of prerequisites, typical scenarios, or when not to use it.

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