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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It lists returned aggregates but does not explicitly confirm this is a read-only operation, mention whether calling it consumes credits, or describe response structure, failure behavior, or data freshness.

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 compact line that front-loads the core concept and lists the meaningful stat categories with no filler or repetition. Every element adds value for a simple one-parameter tool.

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 simple stats tool, the description gives a useful list of output categories, but it lacks an output schema and does not explain the shape of the response or how these stats relate to the search. The absence of usage differentiation from sibling stats tools also leaves some context incomplete.

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, search_id, is a required string with no schema description, giving the agent zero schema-level guidance. The title and description partially compensate by indicating the parameter identifies a Signal Search, but they do not explain how to obtain or format that ID.

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 title and description together clearly identify the tool as returning persona stats for a specific Signal Search, listing concrete output categories such as total personas, top_companies, and credits_spent. It is distinguishable from many siblings by its focus on persona-level aggregates, though it does not explicitly contrast itself with similar stats tools like sdr_signal_stats.

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 guidance on when to use this tool over the many related sdr_* statistics and search tools. The description implies it is for aggregated persona stats for a search, but it never states conditions, alternatives, or exclusions.

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