list_console_messages

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

Annotations already establish readOnlyHint=true, so the safety profile is covered. The description usefully adds the temporal boundary ('since the last navigation') that defines what the list contains, but says nothing about pagination or preserved-message behavior beyond what the schema already documents.

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. It is efficient and readable, though it does not exploit the space to add routing or behavioral context.

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 read-only listing tool with 100% schema coverage and a readOnlyHint annotation, the description covers the essential purpose and scope. No output schema exists, yet the temporal scope gives the agent enough to call it correctly; only the sibling relationship is omitted.

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 coverage is 100%, so all seven parameters (types, pageId, pageIdx, pageSize, serviceWorkerId, includeStackTraces, includePreservedMessages) are documented in the schema itself. The description adds no parameter detail, which is acceptable given full coverage — baseline 3.

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?

States a specific verb (List) and resource (console messages) with an explicit temporal scope ('since the last navigation'). This is clearly distinguishable from the singular get_console_message by scope, though that sibling relationship is not called out in the text.

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 gives no when-to-use guidance, no prerequisites, and does not name the alternative get_console_message for retrieving a single message. The temporal scope is stated but that is a filter, not usage guidance.

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