get_shop

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

There are no annotations, so the description carries the full burden of disclosing behavioral traits. It simply states 'Return basic information' without mentioning any side effects, permissions, rate limits, or potential gotchas. Even though the tool is a simple read operation, the description does not explicitly confirm that it is read-only or disclose any operational behavior beyond the action itself.

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, clear sentence that immediately conveys the tool's purpose. There is no fluff or redundant information. Every word contributes to understanding what the tool does, making it an excellent example of concise, front-loaded communication.

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 (no parameters, output schema exists), the description is reasonably complete. The output schema likely details the return structure, so the description does not need to enumerate fields. However, it could have added a bit more context about what 'basic information' entails or any prerequisites, but for a straightforward getter, this is adequate.

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?

The tool has zero parameters, so the baseline is 4 as per the rubric. The description adds no parameter details because none exist. The schema is automatically fully covered since the property list is empty. The description's mention of 'basic information' aligns well with the tool's function and requires no further parameter explanation.

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 clear action and resource: 'Return basic information about the connected Shopify shop.' It is distinct from the sibling tools (list_products, get_product, list_orders) which target products and orders, so there is no ambiguity about what this tool does. The phrase 'basic information' is somewhat generic but does not detract from the clarity of the overall 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?

The description provides no guidance on when to use this tool versus alternatives. It does not mention any conditions, exclusions, or scenarios where another tool might be more appropriate. For example, it does not say 'use this to retrieve shop-level settings' or contrast it with product/order tools. The only implicit guidance is that it is for shop info, but no explicit 'when to use' is given.

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