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

Annotations already declare readOnlyHint and openWorldHint, so the safety profile is covered. The description still adds genuine behavioral context beyond that: this returns the *latest* filing only (temporal scoping) and results come pre-sorted by position value, which the agent cannot get from the annotations.

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 tight sentence with the resource, identifier, and ordering front-loaded. No filler or redundancy; every clause carries information.

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 an output schema present, return fields need not be described, and the readOnly annotation covers safety. The description supplies resource, identifier, cadence (latest) and ordering, leaving only minor gaps like pagination behavior and what 'latest' means across filing quarters.

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 both parameters are already documented in the schema. The description restates that CIK identifies the institutional manager but adds no syntax, format, or limit guidance, so baseline 3 applies.

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 gives a specific verb and resource (returns 13F-HR institutional holdings) plus the identifier (CIK) and the ordering (sorted by position value). This is enough to distinguish it from generic sec_* siblings like sec_financials or sec_insider, but it never names a nearby alternative such as datasets_sec_institutional_positions_search, so differentiation is inferred rather than stated.

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 use case is implied clearly (look up an institutional manager's holdings by CIK), but there is no explicit when-to-use, when-not-to-use, or alternative tool named. The agent must infer it should pick this over the datasets_sec_* counterpart without help from the description.

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