get_supplier_details

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

No annotations are provided, so the description carries full burden. It implies a read-only operation but does not disclose authentication needs, error behavior, or limitations. The description does not clarify if the tool supports partial matches or what happens when multiple suppliers are found.

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?

A single sentence front-loaded with the verb and object. Every word is necessary and no redundant information. Excellent conciseness.

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 simple nature (2 optional params, output schema exists), the description is minimally complete. It hints at return fields but does not explain search behavior or edge cases. Without output schema content, the description could benefit from clarifying that the tool can search by name or keyword.

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 covers 100% of parameters with descriptions and examples. The description adds context about returned fields but does not clarify parameter interaction (e.g., exclusivity or precedence). Baseline 3 is appropriate as the description adds minimal value beyond the 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?

The description clearly states 'Get complete supplier details' with specific fields (address, phone, contacts). The verb+resource is clear, and the name differentiates it from sibling tools like get_customer_details. However, it does not explicitly distinguish from other get_*_details 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. It does not mention when not to use it, nor does it provide context for choosing between name and keyword parameters. The description is generic and lacks usage protocol.

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