list_templates

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

The annotations already declare readOnlyHint, idempotentHint, and destructiveHint, so the safety profile is covered. The description adds real value by disclosing that 'permissions and allowedTokens are advisory metadata' and not enforced, preventing the agent from treating returned labels as authoritative restrictions.

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 concise and every sentence earns its place: the first states the operation and scope, and the second warns about the advisory nature of returned metadata. There is no filler or redundant wording.

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 zero-parameter, read-only listing tool, the description covers the main things an agent needs: what is listed, where it comes from, and what semantics to apply to the returned metadata. It does not mention what happens when no active grab session exists, but the description is otherwise sufficient.

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 tool has zero parameters and the schema covers all of them, so there is no parameter documentation gap to compensate for. The description's active-grab-session scoping is contextual, not parameter guidance, making the zero-parameter baseline the right choice.

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 opens with the verb 'List' and clearly names the resource: templates and their registered page pathnames from the active grab session. This is a specific, clear operation. It does not explicitly differentiate itself from nearby siblings like get_page_template, though the plural 'List' and 'registered pathnames' imply a broader listing.

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 phrase 'from the active grab session' gives a meaningful scoping cue and implies the tool is meant for sessions started with start_grab_session. However, no explicit when-to-use or when-not-to-use guidance is provided, and no alternative tools are named. Usage is mostly implied rather than directly instructed.

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