nexo_protocol_debt_resolve

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

No annotations provided; description only says 'resolve', implying a mutation. Lacks details on side effects, reversibility, or idempotence. Minimal behavioral disclosure beyond the verb.

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?

Extremely concise (one sentence), but lacks structure (e.g., bullet points or examples). Not wasteful, but could be better organized.

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?

6 parameters, no output schema, no annotations. Description omits return values, side effects, required context (e.g., session_id usage), and does not clarify resolution types. Severely incomplete.

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%. Description mentions only 'id' and 'filters' vaguely, failing to map to any of the 6 parameters (debt_id, task_id, debt_ids, debt_types, resolution, session_id). No parameter explanations.

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 uses specific verb 'resolve' and resource 'protocol debt records', and indicates two modes ('by id or filters'). It clearly states the tool's action and scope, though it does not differentiate from sibling tools.

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. The description mentions id/filters but provides no context for choosing between them or prerequisites.

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