commerce_supplier_search

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

With no annotations, the description must fully disclose behaviors. It mentions routing through a domain-agent dispatcher and scope (JWT, tenant, company), but does not state whether the action is read-only, modifies state, or what response format is expected. Transparency is insufficient.

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?

The description is short (three sentences) but includes routing details that may not help in tool selection. The first sentence is redundant with the tool name. It could be more informative while remaining concise.

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 tool's simplicity (2 optional params, no enums, output schema exists), the description should explain when to use it and what results to expect. It lacks guidance on usage context, return values, and differentiation from similar tools, making it 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%, so the description must compensate. The Args section describes 'message' as 'Free-text objective' and 'inputs' as 'Optional JSON string of structured inputs,' adding some meaning. However, the descriptions are vague and do not specify valid formats, constraints, or examples, leaving significant ambiguity.

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 states 'Run the commerce domain agent action supplier_search,' which is nearly tautological with the tool name. It does not explicitly state that the tool searches for suppliers, requiring inference. The routing details do not clarify the core purpose.

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 is provided on when to use this tool versus sibling tools like commerce_supplier_evaluation or commerce_procurement_brief. The description lacks context for appropriate use cases or exclusions.

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