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

Annotations already declare readOnlyHint=true and openWorldHint=true, and an output schema exists, so the safety and return-shape burden is largely covered. The description adds that results are aggregated rather than row-level, which is useful, but says nothing about the aggregation semantics (counts, top-N, ordering).

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 front-loaded sentence with no filler; the parenthetical clarifying facet dimensions is the only added content and it earns its place. It is efficient, though minimal rather than exemplary.

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 7 parameters, an output schema, and annotations, the structured fields carry most of the load, but the description leaves out how this tool relates to its search sibling and how the aggregation should be consumed. Adequate but with a clear routing gap.

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 100%, so the schema already documents all 7 parameters including the required facet enum values (manager, issuer). The description only restates the facet dimensions and adds no syntax, default, or interaction detail beyond what the schema provides.

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 names a specific operation (facet aggregation) and resource (SEC institutional positions dataset) and even flags the two facet dimensions (manager or issuer). It does not distinguish itself from the sibling datasets_sec_institutional_positions_search, so an agent must infer the split between aggregation and record retrieval.

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 explicit when-to-use guidance. 'Facet aggregation' hints that this returns grouped counts rather than records, implying it precedes or complements a search, but no alternative tool is named and no condition selecting this tool over search is stated.

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