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

No annotations are provided, so the description carries the full burden and does so thoroughly: read-only feed semantics, one row per (issuer, person), flags and title from the most recent filing, newest-first cursor pagination up to 1000/page, and caveats like 'filed roster, not scraped bios' and 'never an assessment.' No contradictions with 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?

Every sentence earns its place: scope question, data source and row grain, ordering and pagination, filter capabilities, and data-source caveats. The core purpose is front-loaded before implementation details, and there is no filler.

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?

Even without an output schema, the description states what each row represents (issuer/person, officer/director flags, title, ticker/CIK) and how results are ordered and paginated. Together with the fully documented schema, this is sufficient for an agent to select and invoke the tool correctly.

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 input schema has 100% description coverage with examples for all 8 parameters, so the baseline is 3. The description's filter list ('role, ticker, title fragment, person state, issuer CIK, or since') mostly summarizes schema fields rather than adding new meaning. The schema itself handles parameter semantics well.

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 opens with a concrete data need ('Who are the current executives and directors...') and specifies the source (Section 16 filings, Forms 3/4/5) and row grain. It differentiates from sibling SEC tools by emphasizing the officer/director roster and 'filed roster, not scraped bios.'

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?

Clear context is provided: use when a current SEC-attested officer/director roster for US public companies is needed, with bulk feed filtering and pagination. However, it does not explicitly name sibling tools such as sec_feed_insiders or sec_insiders_transactions, or state when not to use them.

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