get_picklistOne picklist: assigned picker, line references, group key, timestamps, and a short-lived pick-PDF link.
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | The picklist id. |
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true and destructiveHint=false, covering safety. The description adds useful behavioral context by noting the pick-PDF link is 'short-lived', which is not inferable from annotations or the schema. It also lists the returned fields, giving the agent a clear picture of the output without needing to inspect the output schema.
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 a single, concise sentence that front-loads the key idea ('One picklist') and efficiently lists the main fields. Every word adds value, with no redundancy or filler.
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 get-by-id tool with 1 parameter, full schema coverage, and an output schema, the description provides sufficient context: it identifies the resource, the key fields, and the short-lived link. The annotations confirm safety, and the output schema covers return values, so no additional explanation is needed.
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% – the 'id' parameter is described as 'The picklist id.' The description does not add any additional meaning beyond this, so it relies on the schema for parameter semantics. Baseline 3 is appropriate given the schema fully documents the parameter.
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 opens with 'One picklist' which clearly indicates this tool retrieves a single picklist's detail, and the title 'Get picklist detail' provides a specific verb and resource. It distinguishes from sibling tools like list_picklists by focusing on a single instance with specific fields.
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?
The description implies the tool is used when you need details for a specific picklist (e.g., after obtaining an ID via list_picklists), but it does not explicitly state when to use it over alternatives or mention any prerequisites. There is no direct comparison to list_picklists or other sibling tools, so guidance is only implied.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Most tools target distinct data points (e.g., get_analytics_summary vs get_brand_score). However, 'search' and 'search_catalog' have overlapping functionality and could cause confusion, and 'fetch' is a helper tied to 'search', adding minor ambiguity.
The majority use consistent verb_noun snake_case (e.g., get_inventory, list_stores). Exceptions like 'fetch' and 'search' (without object) break the pattern, but they are few.
43 tools is excessive for a data-retrieval-only API. Many get_* and search_* tools could be consolidated (e.g., search_catalog, search_inventory, search_orders are similar). The large number will overwhelm an agent.
The tool set is entirely read-only (get, search, list, fetch). There are no create, update, or delete tools, which is a critical gap for managing e-commerce operations. Agents can only view data, not act on it.