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

Annotations already cover read-only, idempotent, non-destructive and open-world, so the bar is lower; the description still adds real context: EDGAR as source, every row linking to its filing, a leading one-line answer with a date, and truncation signalled via total/returned and a `more` link. It stops short of describing row fields, but the safety and provenance picture is solid.

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 question is front-loaded and the whole thing is two short lines, but 'Charter Amendments.' restates the tool name and the middot fragment 'SEC 8-K Item 5.03 · articles, bylaws, fiscal year · renames flagged' repeats the title, so a little space is not earning its place.

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 and a single well-documented parameter, the description carries the return-shape burden and mostly does: leading one-line answer plus date, per-row filing links, and truncation signalling. Only the actual row fields are left unspecified.

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?

Only one optional parameter and the schema already documents it fully (default 50, ceiling 200, total/returned/truncated, `more` link). The description adds nothing about `limit` beyond the schema, so 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?

Names a specific verb-frame ('Answers: Which public companies changed their name, charter or bylaws this week?') plus the exact SEC trigger (8-K Item 5.03, articles/bylaws/fiscal year/renames). Because every sibling covers a distinct topic (mergers, IPO watch, cyber disclosures), the resource scope alone distinguishes it cleanly.

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 framing as a question with 'this week' gives a clear condition for use — weekly charter/bylaw/rename changes — and the SEC EDGAR sourcing sets expectations. It does not name an exclusion or an alternative sibling, so it stops short of the 5 bar.

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