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

Annotations already declare the full safety profile (readOnly, idempotent, non-destructive, closed-world), so the description only needs to add context. It does add the return payload fields (title, date, summary line, URL), which is useful since there is no output schema, but it says nothing about pagination, rate limits, or ordering beyond 'most recent'.

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 sentence with no filler; the resource and its scope are front-loaded, and the return fields are appended compactly rather than as a separate list.

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 simple two-optional-parameter read tool with no output schema, the description covers purpose, the two result kinds, and the returned fields. The only gap is that it does not say what happens if no briefs exist or how results are ordered.

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 100%, so both the enum for 'kind' and the limit bounds/default are already documented. The description's 'or Weekly Briefs' phrasing loosely maps to the enum values but adds no syntax, formatting, or behavioral detail beyond the schema, so the baseline of 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 resource (Koreanics Bill Briefs / Weekly Briefs) and a scope qualifier (most recent), and glosses what a bill brief actually is. It is clearly distinct from every sibling (get_bill, list_laws, search_bills, etc.), though it is phrased as a noun phrase rather than an explicit verb+resource.

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 only implied: the mention of two brief kinds tells the agent this tool spans both, and the schema supplies the default (bill). There is no statement of when to prefer this over search_bills or get_bill, nor any exclusion or prerequisite.

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