rezdy_agent_get_suppliers

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

No annotations provided, so description carries full burden. 'Get' implies read-only, but description doesn't confirm safety, pagination behavior for 'all' results, rate limits, or return structure. 'All' suggests unfiltered retrieval without mentioning performance implications or result set limits.

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?

Four words, zero waste. Single sentence front-loaded with action and target. No redundancy or filler content.

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?

Adequate for a zero-parameter tool, but 'get all' operations typically require pagination or limit documentation which is absent. No output schema means return structure should be described but isn't. Sufficient to identify the tool's basic function but lacks operational context.

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?

Zero parameters present with empty input schema. Per scoring rules, baseline is 4 for tools with no parameters. Description implies no filtering is possible (consistent with 'get all'), which matches the empty 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?

Clear verb ('Get') + resource ('marketplace suppliers') with explicit scope ('all'). Distinguishes from siblings like get_product, get_customer, and get_categories by targeting suppliers specifically. Lacks detail on what constitutes a 'marketplace supplier' in this 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?

No guidance on when to use versus alternatives (e.g., whether suppliers are returned via search_products or if this is the only supplier endpoint). No mention of prerequisites, permissions, or when not to use the tool.

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