theotown_get_draft_catalog

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

No annotations are supplied, so the description carries the full burden. 'Search and list' does successfully convey that this is a non-mutating read, which is the key safety trait for this tool, but nothing is said about match semantics (substring vs exact), result limits, or whether the catalog is scoped to a game session.

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?

One short sentence, front-loaded with the action and immediately followed by the resource domain. There is no filler, though it is arguably terse to the point of leaving gaps rather than dense with useful information.

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?

The tool is simple (two optional params, an output schema exists so return values need no explanation), and the description covers the basic purpose. It is nevertheless thin for a no-annotation tool, since parameter behavior and its role relative to the build tools are both 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?

Both parameters have 0% schema description coverage and neither is mentioned in the description. The enumerated item types (drafts, buildings, roads, utilities) hint at plausible values for the category parameter, but the query parameter's matching behavior is left completely undocumented.

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 gives a specific verb pair ('Search and list') plus the resource domain (drafts, buildings, roads, utilities), which is enough to tell it is a read-only catalog lookup rather than one of the build_* siblings. It stops short of explicitly contrasting itself with those siblings, but the purpose is unmistakable.

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?

There is no when-to-use guidance at all: nothing says this should be called before theotown_build_building or theotown_build_road to resolve an item, and nothing states exclusions or prerequisites. An agent must infer the discovery-then-build workflow entirely on its own.

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