cm_get_segment

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

Annotations declare readOnlyHint=true, so the description's 'Get' aligns with that. Beyond annotations, the description specifies the three pieces of data returned, adding context about the response. This is sufficient for a simple read tool.

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 of 12 words, no filler, and front-loaded with the key verb and resource. Every word earns its place.

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's simplicity (one required parameter, no output schema), the description adequately lists the return fields. It could mention error handling or lack of subscriber data, but for a basic read tool with annotations, it is fairly 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?

The only parameter, segmentId, has a schema description 'Segment ID.' The tool description does not add further meaning. Schema coverage is 100%, so baseline is 3; no extra value from the description.

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 verb 'Get' and resource 'segment', and specifies the exact data returned: name, list ID, and active subscriber count. This distinguishes it from sibling tools like cm_get_segment_subscribers (which returns subscribers) and cm_get_client_segments (which lists 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?

The description implies when to use the tool (to retrieve basic segment info) but does not explicitly state when not to use it or mention alternatives. Siblings like cm_get_segment_subscribers and cm_update_segment have different purposes, but no guidance is provided. This is adequate but not explicit.

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