nexo_goal_open

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

No annotations provided. The description claims durability and explicit objectives but fails to disclose side effects, prerequisites, or return behavior. Insufficient for a mutation tool.

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 17 words is too brief; it omits critical information. Conciseness is not beneficial when it sacrifices completeness.

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?

Missing output schema. Description does not clarify what happens on open (e.g., returns goal ID?), nor does it cover parameter defaults or behavior. Incomplete for a 9-parameter tool.

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%. The description does not explain any of the 9 parameters (sid, title, objective, etc.), relying on names alone. The agent gets no help understanding parameter semantics.

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 verb 'open' and resource 'durable goal', and explains the purpose: to keep multi-session objectives explicit. It distinguishes from sibling tools like nexo_goal_get (retrieve) or nexo_goal_update (modify).

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?

Only implicitly suggests use when objectives should persist across sessions and contrasts with notes. No explicit when-to-use or when-not-to-use, no alternatives compared.

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