customers_segments

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

With no annotations, the description must reveal behavior. It does disclose the upgrade requirement, a real constraint, but it says nothing about what the tool does, side effects, or what happens when invoked without the higher plan.

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 short, front-loaded sentence. It is efficient and immediately communicates the upgrade gate, though it lacks substantive tool information.

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?

Even for a simple parameterless tool, a complete description should state its purpose. This description only warns about licensing and points to another tool, leaving the actual function of `customers_segments` completely unexplained.

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 an empty schema with 100% coverage. The baseline for 0 parameters is 4, and no parameter details are needed.

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 never states what the tool does. "Upgrade required" only communicates a licensing restriction, not the tool's function of managing or retrieving customer segments.

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?

It directs the user to call `license_status` to see options, which is a remediation step for the upgrade requirement, but it gives no guidance on when to use `customers_segments` itself or how it fits among sibling tools.

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