nexo_pre_action_context

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

No annotations are provided, so description must carry the burden. It mentions 'build' (likely read-only) but does not disclose side effects, data sources, or what the bundle contains. Vague on whether it modifies state.

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?

Two sentences, concise and front-loaded. No fluff, but could be more structured with bullet points for parameters.

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 the complexity of the tool ecosystem and no output schema, the description is insufficient. It does not explain what a 'context bundle' is, how to interpret results, or how this tool differs from many similar context-tools (e.g., nexo_recent_context, nexo_context_packet).

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?

The input schema has 5 parameters (query, context_key, session_id, hours, limit) with 0% description coverage. The description adds no information about any parameter, leaving the agent to infer from names alone.

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 builds a '24h recent-context bundle' to review before acting, using specific verb and resource. It also hints at use cases (emails, orchestrators), but does not explicitly differentiate from other context tools like nexo_context_packet or nexo_recent_context.

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?

Implied usage is provided: 'should be reviewed before acting' and 'especially useful for emails, orchestrators'. However, no explicit guidance on when not to use or alternatives among the many sibling tools.

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