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

With no annotations, the description carries the behavioral disclosure burden. It does add useful context: raw taxonomy, per-subject bill counts, scoping by state, narrowing by q. However, it does not mention auth, rate limits, pagination, or the exact output shape, leaving some behavioral details implicit for a read-only list tool.

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?

Three sentences, all load-bearing: first identifies the resource, second explains the taxonomy and relationship to list_topics, third gives explicit use cases. No wasted words and the most important context is front-loaded.

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 low-complexity, zero-required-param list endpoint, the description covers purpose, sibling distinction, use cases, and filtering behavior. It mentions per-subject bill counts and the subject_id use case, which partially compensates for the missing output schema, though pagination/ordering details are absent.

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%, so the schema already documents all three parameters. The description adds the 'scope with state, narrow with q' relationship, but this is mostly a restatement of the schema's own descriptions rather than significant new meaning.

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 clearly identifies the resource ('raw subject taxonomy with per-subject bill counts') and the specific operation (GET /v1/subjects). It also explicitly distinguishes subjects from the curated topic slugs in list_topics, so an agent can tell this tool apart from its closest sibling.

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?

It states concrete use cases: finding a subject_id to filter search_bills by, or gauging what a jurisdiction is legislating on. It also names the sibling tool list_topics and explains the key difference, giving the agent clear routing guidance.

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