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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds scope ('visible to a subaccount') and the includePrebuilt filter semantics, but omits pagination behavior, default result ordering, or return shape, which is acceptable given the read-only annotation but still leaves gaps.

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?

Two short sentences, front-loaded with the core action and followed by the most useful filter hint. No wasted text.

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 list tool with five parameters, no output schema, and 0% parameter descriptions, the description is incomplete. Pagination via limit/cursor, search semantics, and required subAccountId behavior are not explained.

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% across 5 parameters, so the description should compensate but only explains includePrebuilt. It leaves subAccountId, limit, cursor, and search undocumented, making it hard to invoke correctly without inspecting the schema.

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 and resource ('List tools') plus scope ('visible to a subaccount'), so the agent can distinguish it from mutation siblings like tools_create_custom or tools_update. It does not explicitly distinguish it from search_tools, which limits it to a 4.

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?

Provides useful guidance for one parameter ('Pass includePrebuilt=false for only custom tools'), but does not say when to use this versus search_tools or tools_get, nor any exclusions or prerequisites.

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