cigchat_shop_locations_get_info

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

With no annotations provided, the description carries the full burden. It discloses the required scope, which is useful context, and the 'Get' verb implies a read-only operation. However, it does not describe response format, error behavior, or any other side effects.

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 one sentence that packs the action, endpoint, and auth requirement with zero waste. It is appropriately front-loaded, and the typo does not affect overall structure.

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 one-parameter get tool, the description covers the essential call path and permission requirement. However, it does not state what 'location info' includes, and with no output schema, the agent lacks full context about expected return data.

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 input schema fully documents the single parameter (locationId) with a description, so the baseline is 3. The description adds no extra parameter meaning beyond referencing the locationId in the endpoint path.

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 action ('Get lcoation info') and the resource (shop location), with the HTTP endpoint disambiguating it from list-style siblings like cigchat_list_shop_locations. The typo 'lcoation' is minor and does not obscure the intended meaning.

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 gives an explicit auth prerequisite (Manage Team scope) but provides no explicit when-to-use guidance or exclusions. The purpose is clear enough to infer usage, but it does not mention alternatives or contrast with listing operations.

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