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

Annotations already cover the safety profile (readOnly, non-destructive, closed-world), so the lower bar applies. The description adds genuine behavioral context beyond the annotations: the schema is 'frozen' and 'additive-only', and the design rules (strings-as-filed, null-never-missing) tell the agent what guarantees the data contracts hold.

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 dense sentence that front-loads the resource ('the frozen schema-v1 contract for FilingPulse objects') then lists contents via a colon. No filler, no redundancy, appropriate length for a reference tool.

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 no output schema, the description must convey what a caller gets back, and it does so by naming the sections and design rules. For a one-parameter, read-only reference tool this is nearly complete; only the 'overview' default value and a hint that this is static documentation are not spelled out.

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 enumerates content areas matching five of the six enum values (form4, event_8k, registration_event, list envelope, transaction_codes), with 'design rules' implicitly covering the default 'overview' section. It could be sharper about the default, but the mapping is largely recoverable.

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 resource (the frozen schema-v1 contract) and enumerates exactly what it documents: form4, event_8k, registration_event, the list envelope, design rules, and the transaction-code table. This clearly separates it from all sibling tools, which fetch data rather than describe the data contract.

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?

Usage is implied rather than stated — an agent infers it should call this to learn the schema before interpreting other tools' output. There is no explicit when-to-use or when-not-to-use guidance, nor any statement that this is a prerequisite/companion to the sibling data tools.

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