sherweb_customers_get

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It doesn't state what happens if the customerId is invalid or nonexistent (error vs empty result), whether authentication/authorization is required, or what the response structure looks like. For a retrieval tool with zero annotation coverage, the description should disclose more behavioral context.

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?

Single sentence, no filler words, front-loaded purpose. It's appropriately terse for a simple single-resource fetch operation. Could arguably add details, but for a one-parameter get tool, this length is appropriate.

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 1-parameter single-resource getter, the description is reasonably complete. The schema covers the parameter fully, and the purpose is clear. However, with no annotations and no output schema, it could benefit from noting response structure or error behavior. Given the tool's simplicity, this is adequate but not comprehensive.

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 'The unique customer ID' for the only parameter. The one parameter is self-explanatory and well-described in the schema itself. The description reinforces that customerId is the lookup key but doesn't add much beyond the schema, which is sufficient given full coverage.

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 verb 'Get' plus 'detailed information about a specific customer by their ID' clearly identifies a single-record retrieval operation. It distinguishes from the sibling sherweb_customers_list, which presumably returns a collection. However, it doesn't explicitly contrast with the list sibling or specify what 'detailed' means relative to list results.

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 this is for when you need details about one specific customer (as opposed to listing customers), which provides some usage context. However, there are no explicit when-to-use/when-not-to-use statements, exclusions, prerequisites, or alternatives mentioned. Related siblings like subscriptions_get exist, suggesting a pattern, but no guidance is given on choosing between them.

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