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

Annotations already establish readOnlyHint=true and destructiveHint=false. The description adds meaningful behavioral context beyond those annotations: the schema is 'frozen', 'additive-only', and governed by design rules such as strings-as-filed and null-never-missing. This gives the agent a stable-contract expectation without contradicting 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?

The description is a single dense sentence that front-loads the core purpose ('frozen schema-v1 contract') and then uses a colon-delimited list to enumerate scope. Every phrase earns its place, though the long list makes it slightly heavy.

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 one-parameter, read-only reference tool with no output schema, the description covers the schema's contents, stability, design rules, and relevant sections. The only minor gap is not naming the 'overview' section explicitly, but the description otherwise provides sufficient context for correct invocation.

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 does partially by naming most enum-related content areas—form4, event_8k, registration_event, list_envelope, transaction_codes—and adding context about design rules. However, it does not explicitly map each enum value to its content or clarify what the default 'overview' section contains.

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 identifies a specific resource—the frozen schema-v1 contract for FilingPulse objects—and enumerates its contents (form4, event_8k, registration_event, list envelope, design rules, transaction-code table). This clearly distinguishes it from the sibling data-retrieval tools, though it lacks an explicit verb such as 'retrieves' or 'returns'.

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 description does not state when to use this tool versus the sibling data endpoints, nor does it provide any explicit when-to-use/when-not-to-use guidance. The intended use is only implied by the word 'reference' and the enumerated schema contents.

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