nexo_outcome_pattern_candidates

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

No annotations provided. Description indicates a read-only operation (list) and mentions the data source (cortex-linked decisions) and criteria (consistent enough). However, it does not disclose side effects, authorization needs, or rate limits. For a simple listing tool, this is minimally adequate.

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?

Single sentence, front-loaded, no redundancy. Every word earns its place.

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?

The description covers the tool's purpose and data source but omits parameter details. For a tool with 2 parameters and no output schema, more completeness is expected.

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% (no descriptions in the input schema). The tool description does not explain the parameters (min_resolved, limit) or their defaults. While parameter names are somewhat intuitive, the description fails to add meaning beyond the schema.

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 the tool lists repeated resolved outcome patterns from cortex-linked decisions, distinguishing it from siblings like nexo_outcome_list (outcomes) and nexo_outcome_pattern_capture (capture patterns). The verb 'list' and resource 'outcome pattern candidates' are specific.

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. Siblings like nexo_outcome_list, nexo_outcome_check, or nexo_outcome_pattern_capture exist but no comparison or context is provided.

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