cigchat_shop_business_hours_info

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

No annotations are provided, so the description carries the full burden. It discloses the HTTP method (GET) indicating a read-only operation and the required auth scope. However, it does not describe the response format, error behavior, or any potential side effects, leaving some uncertainty about what the agent can expect after calling.

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 sentence that leads with the core action 'Get store business hours', then concisely includes the endpoint and auth requirement. Every word adds value, with no redundancy or unnecessary detail.

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, no-parameter getter with no output schema, the description provides adequate context: the purpose, endpoint, and authentication requirement. It could optionally mention that the response contains the hours data, but the function name and endpoint make this highly obvious. The tool is simple enough that the description is largely complete.

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?

With zero parameters and an empty schema (100% schema description coverage), there is nothing for the description to add about parameter semantics. The baseline of 4 for zero-parameter tools applies, as the description correctly omits any parameter details.

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 the tool's function: 'Get store business hours'. It specifies the HTTP endpoint 'GET /shop/business-hours/info' and distinguishes itself from sibling tools like 'cigchat_shop_business_hours_update' through the verb 'Get' versus 'Update'. This is a specific verb+resource construction.

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 does not explicitly state when to use this tool versus alternatives, nor does it mention any exclusions. It does provide a prerequisite ('Requires the Manage Team scope'), which implies the tool is for authenticated read access, but no guidance on when to prefer it over similar tools. Usage context is present but implied rather than explicit.

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