nexo_user_state

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

No annotations provided. Description implies read operation but does not confirm side effects or safety. Lacks disclosure of whether it modifies state or is purely observational.

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 concise sentence with no redundancy. However, brevity sacrifices important details, making it under-specified.

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 annotations, no output schema, and 2 undocumented parameters, the description is insufficient. It does not explain return format, side effects, or when to invoke.

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 has two parameters (days, persist) with 0% description coverage. Description does not explain their purpose or behavior, failing to add value 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?

Description clearly states verb 'Compute' and resource 'user-state snapshot' with specific inputs (trust, corrections, sentiment, hot context). Differentiates from sibling tools like nexo_user_state_history and nexo_user_state_stats by focusing on current snapshot.

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 versus alternatives. Does not mention conditions, prerequisites, or when not to use.

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