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

With no annotations, the description carries the behavioral burden. It discloses that only markets with meeting records are included and that q filters by slug or name, but it does not state the return shape, pagination behavior, or matching semantics. It is acceptable but not thorough.

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 entire description is one short, front-loaded sentence that states the resource, the relevant condition, and the filtering parameter without wasted words.

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 one-parameter list tool, the description is mostly complete, but the absence of an output schema and annotations means an agent still lacks details about the response format, fields, and any pagination or sorting behavior. It is sufficient for basic invocation but not fully complete.

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?

The schema provides only a default q string with no description, so the description adds meaningful semantics by stating that q filters by slug or name and is optional. It could clarify whether matching is exact or partial, but it compensates well for the 0% schema description coverage.

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 as markets (cities/counties) with meeting records, and the tool name provides the 'list' action. It is distinct from siblings like search_meetings or search_officers because no other sibling covers market listing, though it could be more explicit about returning a list.

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 implied: use this tool when you need markets that have meeting records. However, there is no explicit guidance about when to prefer this over a sibling tool, no alternatives are named, and no exclusions are stated.

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