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

Annotations already declare readOnly/idempotent/non-destructive, so the safety burden is covered. The description adds genuine context: SEC EDGAR source, no API key required, one record per position, and the _has_more pagination signal. It doesn't discuss rate limits or caching, but it goes meaningfully beyond 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?

Front-loaded with purpose, then a labeled field list, then usage notes in short imperative sentences. The per-field return list is somewhat long and partly redundant with the output schema, but the structure keeps it scannable.

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 read-only parsed-filing tool with an output schema and annotations, the description covers prerequisites, pagination, filtering, and source. The only substantive gap is the undocumented secondary parameters, which the description never acknowledges.

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 description explains min_value_thousands, sort_by, limit/offset, and the cik/accession_no inputs well. However, it is silent on several schema fields bundled into the params object (wholesaler_ids, exclude_fillers, source_resource_id, optional_additional_filters, mcp_prompt_id), leaving their relevance to this EDGAR tool unexplained.

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?

States a specific verb+resource+scope: 'Fetch and parse the complete equity holdings table from a specific SEC 13F-HR filing.' It also positions itself relative to siblings by naming SearchEdgar13F and GetEdgarCompanyFilings as the discovery step that feeds this tool.

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?

Explicit routing is given: 'PRIMARY USE: Step 2 of institutional holdings workflow... Obtain cik and accession_no from SearchEdgar13F or GetEdgarCompanyFilings, then call this tool.' It also tells the agent when to filter (min_value_thousands), how to sort, and how to paginate with limit/offset and _has_more.

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