Continue Product Listing

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

Annotations indicate readOnlyHint=false so the tool modifies state, but the description does not elaborate on side effects (e.g., saves conversation state) or requirements (e.g., authentication). The description adds limited behavioral context beyond annotations.

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, front-loaded with the verb and resource. Every sentence serves a purpose: stating the action, input format, and next step. No wasted words.

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?

Describes the immediate action and next step, but does not mention what the tool returns (no output schema) or any conversational flow details (e.g., how to check 'ready_to_submit'). For a continuation tool, some gaps in completeness.

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?

Input schema covers both parameters with descriptions. The description does not add extra parameter info, but the schema descriptions are meaningful (e.g., 'Conversation ID from nanmesh.listing.start'). Given 100% coverage, rating above baseline.

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?

Clearly states the action 'Continue a product listing conversation' and the mode 'Send product details in natural language'. It does not explicitly differentiate from 'nanmesh.listing.start', but the name 'continue' implies the prior step.

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?

Provides a clear when-to-use guidance by referencing the 'ready_to_submit' condition and directing to 'nanmesh.listing.submit' as the next step. It implicitly suggests using after 'start' but lacks explicit exclusion scenarios.

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