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

With no annotations, the description carries the full burden and it covers key behavioral context: $0.05 per call, x402 payment/authentication flow, API-key alternatives, and an educational-data disclaimer. It does not mention rate limits or pagination, so it is strong but not exhaustive.

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 longer than average but well-structured and front-loaded: first the tool's purpose and data, then payment/authentication, then a pointer to get_catalog. Each clause adds necessary commercial/operational context.

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 two-parameter tool with no output schema, the description provides the essential return fields, optional filtering, cost, and auth. The main gap is the undocumented limit parameter, but the otherwise complete context makes the tool safely invokable.

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%, so the description must compensate; it explains the optional symbol filter but is silent on the limit parameter, its default behavior, or value range. This leaves the agent to infer limit from its name and default value.

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 uses a specific action and resource: 'recent institutional 13F position moves' with enumeration of position types (new/increased/decreased/sold) and output fields. This differentiates it from sibling tools like get_institutional_stock by focusing on moves rather than static stock data.

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 intended use is implied by the description ('recent institutional 13F position moves... Optional ?symbol= filter'), and the suggestion to browse the catalog is useful. However, it never explicitly states when to prefer this tool over sibling alternatives like get_institutional_stock or get_congress_trades.

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