Decode an event's commands

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

With no annotations, the description carries the full behavioral burden. 'Render ... as readable lines' implies a non-mutating read, but nothing states that explicitly, nor does it mention permissions, whether the operation fails for missing maps/events, or what the returned lines actually contain.

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?

A single front-loaded sentence with no filler, which is the right size for a simple tool. It is efficient rather than padded, though the terseness is part of what leaves the gaps above.

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?

With no output schema, no annotations, and zero parameter documentation, the description should be doing much more work. It never explains the shape of the decoded output, how mapId/eventId are sourced, or how this differs from the adjacent command tools.

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 description coverage is 0% for three parameters, so the description must compensate and largely does not: mapId and eventId are never mentioned, and pageIndex is only obliquely gestured at by 'a page's command list'. The agent gets no indication of what these identifiers reference or what happens when pageIndex is omitted.

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 concrete verb ('Render ... as readable lines') and a specific resource ('a page's command list'), so the agent knows this is a read/transform operation rather than a mutation. It does not, however, differentiate itself from look-alike siblings such as command_catalog or show_text, so the boundary between them must be inferred.

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 statement, no prerequisite, and no named alternative. The agent must guess that this is the tool for inspecting an already-written command list rather than for authoring (add_commands/set_commands) or enumerating available commands (command_catalog).

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