List registered tile names

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

Adds significant behavioral details beyond annotations: reads a specific file, validates entries, pins revisions, notes weak metadata and empty-file handling. No contradictions with annotations (readOnlyHint, idempotentHint, destructiveHint).

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?

Every sentence adds unique value: defines the registry, validation rules, constraints, edge cases, and read-only nature. No redundant or filler content.

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?

Covers all necessary aspects for a zero-parameter, read-only tool: what it reads, content format, constraints, error handling (missing file), and purpose. With an output schema present, it does not need to detail return format.

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?

No parameters exist (0 params), so the description has no need to add parameter semantics. Baseline 4 is appropriate as the description fully compensates for the absence of param details by explaining the tool's operation.

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?

Clearly states it reads a server-owned registry (specific resource) and explains its purpose of mapping names to tileset/localId. Distinguishes from sibling tools like tiled_list_files or tiled_get_map_summary by focusing on tile name registration.

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?

Explicitly states it is read-only and describes the context where it is useful (referencing tiles by semantic name). Does not exclude alternatives or provide when-not-to-use guidance, but the purpose is clear enough for an agent to decide.

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