nexo_cortex_override

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

No annotations provided, so description must carry burden. It only states 'preserving the recommendation trail', hinting at non-destructive behavior, but lacks details on side effects, permissions, reversibility, or whether the override is immediate or queued.

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 of 11 words conveys core purpose efficiently. Front-loaded with verb and resource, no redundant phrasing.

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?

Lacks explanation of return values (no output schema), parameter semantics, and edge cases. For a tool with three required parameters, description is too minimal to guide correct invocation.

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 description adds no parameter details. Parameters evaluation_id, chosen, reason are undefined. Agent cannot infer what values are expected for 'chosen' or 'reason' without external knowledge.

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?

Description clearly states action 'Override a stored Cortex recommendation' and specifies 'preserving the recommendation trail'. This verb-resource pair distinguishes it from sibling tools like nexo_cortex_decide, nexo_cortex_review, and nexo_adaptive_override.

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 explicit guidance on when to use this tool vs alternatives. The description implies usage for overriding recommendations, but does not mention exclusions, prerequisites, or relationships to other tools like nexo_cortex_decide or nexo_adaptive_override.

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