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

Annotations already carry readOnlyHint and idempotentHint, but the description adds non-obvious behavior: editorial materiality markers are always present in every response regardless of filters, and the response states the basis of the mechanical classifications. This is valuable context beyond the structured annotations and gives the agent accurate expectations.

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 compact and front-loads the core purpose and filter possibilities. The additional sentences about materiality markers and mechanical classifications earn their place by explaining non-obvious response behavior. The opening rhetorical question and slightly ornate wording could be trimmed, but it is not padded.

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?

Given that an output schema exists and annotations cover safety and idempotency, the description supplies the essential behavioral context and filter semantics. The main missing piece is what happens when version ids are omitted and how pagination defaults work, but this is a minor gap for a list operation with structured information present.

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 50%; status, articles, material_only and from_version_id have some schema description. The description adds meaning by tying filters to status/materiality/article range and by interpreting the version pair as 'two published texts'. But limit, cursor, instrument_id and to_version_id remain undocumented in both schema and description, so the gap is only partly compensated.

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 states a specific action and resource: it lists aligned articles with their classifications across two published texts of an instrument, and names the filtering dimensions. It does not explicitly name or contrast sibling tools such as compare_versions, so it falls just short of full sibling differentiation.

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 intended use is implied: call this tool to see what changed across a whole instrument between its two published texts, with filters on status, materiality and article range. However, it gives no explicit when-not-to-use guidance or alternatives, so an agent may not know how to route away from compare_versions or other siblings.

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