Find tiles by explicit semantics

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

Annotations already indicate read-only, idempotent, non-destructive behavior. The description adds behavioral context: it returns bounded TileRefs ordered by local ID, and searches for exact matches. This goes beyond the structured fields.

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 a single sentence that front-loads the purpose. It is efficient but somewhat wordy; still, every part contributes meaning.

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 the tool's complexity (7 parameters, nested query, siblings), the description covers the main purpose and search capabilities but omits the query mode (all/any) and details about startTileId and expected revisions. The output schema exists, so return value explanation is not needed.

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 description explains the query semantics (class and propertyEquals) which maps to the complex query object, but does not cover startTileId, limit, expected revisions. With 43% schema description coverage, more detail would be helpful, but the description adds value for the core parameters.

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 states the tool searches an external TSJ for exact tile classes or serialized scalar properties, returning bounded TileRefs ordered by local ID. It uses specific verbs and resources, and distinguishes itself from siblings like tiled_list_tile_names or tiled_render_tiles by focusing on semantic search.

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 description implies usage for finding tiles by class or property values, but does not explicitly state when to use this tool versus alternatives (e.g., tiled_list_tile_names for listing all names, tiled_render_tiles for rendering). No when-not-to-use guidance is provided.

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