get_customer_id

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

No annotations are provided, so the description carries full burden. It correctly indicates a read operation without side effects and specifies the return fields (customer_id, name). Lacks mention of rate limits or authentication details, but for a simple list tool, it is sufficiently transparent.

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?

Two sentences with front-loaded purpose. Each sentence adds value: the first states the action and resource, the second provides usage guidance and return info. No wasted words.

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 has no parameters and an output schema (though not shown), the description covers the purpose, usage context, and return fields. It is complete for a list operation tool.

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, and schema description coverage is trivially 100%. The description adds no redundant parameter information, which is appropriate. No additional semantics needed beyond what the schema provides.

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 lists Sprout customer IDs accessible by the API token, using specific verbs ('List') and identifies the resource ('Sprout customer IDs'). It distinguishes from sibling tools (list_profiles, list_metrics, etc.) by focusing on customer ID retrieval.

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?

Explicitly states when to use the tool: when SPROUT_CUSTOMER_ID is unknown or to confirm which account the token points at. This guides the agent on appropriate context and implies alternatives (e.g., not needed when customer ID is already known).

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