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

Annotations only declare readOnlyHint and openWorldHint; the description goes well beyond them by disclosing the 50-item cap, authentication/config requirement (SEC_USER_AGENT contact), SEC fair-access pacing, a per-call price of $0.01 USDC on Base, and the x402 wallet requirement. This is exactly the kind of side-effect, cost, and rate-limit context the annotations cannot express.

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?

Four sentences, front-loaded with purpose, followed by exclusions, operational requirements, and pricing. Every sentence carries distinct information; nothing is padded or repetitive.

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?

Despite having no output schema, the description characterizes the return ('filing index entries', up to 50) and covers the non-obvious operational facts (auth, pacing, payment). An agent has everything needed to decide whether it can and should call this tool.

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 coverage is 100%, with form, company and maxItems fully documented in the schema itself. The description restates ticker/CIK and form filtering but adds no format, aliasing, or constraint detail beyond the schema, so the baseline 3 applies.

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 and resource: 'Read up to 50 recent corporate SEC filing index entries by ticker or CIK'. It also scopes what is returned ('index entries') and explicitly excludes filing text, ownership forms and personal filers, so an agent can distinguish it from the sibling paper/document tools without opening the schema.

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?

Gives clear scope conditions and negative guidance ('No filing text, ownership forms or personal filers') plus prerequisites (operator-configured SEC_USER_AGENT, x402-capable wallet). It does not name an alternative tool for excluded use cases, so it falls short of a full when/when-not/alternatives routing statement.

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