audience.hf.get_segment_summary

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

With no annotations provided, the description carries the full behavioral burden, yet it discloses almost nothing: it does not state that this is a read-only operation, whether it requires auth or an account_id, response size, or caching/freshness behavior. The only hint is 'Human-friendly' implying a formatted output, which is thin for a tool with zero annotation coverage.

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?

It is a single short sentence with zero padding, so nothing is wasted, but that brevity reflects under-specification rather than economy. Size is appropriate only in the sense that there is nothing to trim.

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 tool with 4 parameters, no annotations, and no output schema, the description should explain what the summary contains and when to use it. It provides none of that, leaving the agent without enough context to call it correctly or prefer it over siblings.

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 75%, so the schema already explains account_id, include_raw, and direct_client_login; only the required segment_id lacks a description. The description adds no parameter meaning at all, but with high coverage the schema does the heavy lifting, warranting the baseline 3.

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 phrase 'Audience segment summary card' essentially restates the tool name get_segment_summary, and 'Human-friendly ... for UI/LLM' is a vague qualifier rather than a specific verb+resource statement. It does not distinguish this tool from close siblings such as audience.segments.get, audience.hf.segment_health, or audience.hf.segment_perf, so an agent cannot tell which one to pick from this text.

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?

There is no when-to-use guidance, no prerequisites, and no mention of alternatives. Given the dense sibling cluster of audience/hf segment tools, the absence of any routing signal leaves the agent to guess.

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