audience.segments.stats

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

No annotations are provided, so the description carries the full behavioral burden. It discloses only that results are 'best effort' (an unreliability caveat, which is real value), but says nothing about permissions, latency, or return shape for a stats endpoint.

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?

A single fragment of a sentence — this is under-specification rather than conciseness. There is no waste, but also almost no load-bearing content.

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?

With no annotations, no output schema, and 0% parameter coverage, the description would need to do far more work. A mutation-free read tool in a crowded audience.* family is left almost entirely unspecified.

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 0% for two parameters. The description never mentions segment_id (required) and only loosely hints at field names via 'size/status', leaving the 'fields' array undocumented in both description and schema.

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?

Names the resource (audience segment) and the kind of data returned (size/status), which narrows things somewhat. But 'stats' is not a specific operation and it fails to distinguish itself from close siblings like audience.segments.get, audience.hf.get_segment_summary, or audience.hf.segment_health.

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?

No guidance on when to call this versus audience.segments.get or audience.hf.segment_health. The '(best effort)' caveat hints the data may be approximate but doesn't tell the agent when that trade-off is acceptable.

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