bokio_get_supplier

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds that the supplier is returned 'as Bokio returns it' and cross-references supplier invoices, but it does not elaborate on response shape or error behavior beyond what the schema already documents.

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 short sentences, front-loaded with the core action and followed by a useful sibling cross-reference. There is no redundant or filler text.

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?

For a simple read-only single-resource getter with full schema coverage and read-only annotations, the description is nearly complete. The only minor gap is that it does not describe the returned supplier shape, though 'as Bokio returns it' signals a raw upstream representation.

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 100%, with supplierId and companyId both documented in the schema, including the BOKIO_COMPANY_ID default and not-found behavior. The description's phrase 'by id' adds no meaningful parameter detail beyond the schema, so baseline 3 is appropriate.

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 a specific verb and resource: 'Get one supplier by id.' It also distinguishes the tool from sibling list operations by noting that supplier invoices are retrieved via bokio_list_supplier_invoices.

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?

It clearly implies retrieval of a single supplier and points to bokio_list_supplier_invoices for a related but separate resource. The schema further establishes that supplierId comes from bokio_list_suppliers, though the description itself does not explicitly state when not to use this tool.

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