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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, openWorldHint=false, so the safety profile is covered by structured data. The description adds nothing beyond that — no pagination behavior, no indication of ordering, page size limits, or whether an empty result is possible.

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 short sentence with no filler, so it is not bloated. However, the one sentence carries no useful information beyond the tool name, so brevity here reflects thinness rather than efficiency.

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?

There is no output schema and no annotation gap, but a paginated list tool still needs its description to say what is returned and how paging works. With two undocumented parameters and a garbled resource name, the definition leaves the agent guessing.

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%, so the description must carry the burden for page and per_page, but it mentions neither. The schema names the parameters and supplies defaults (1 and 50), which prevents a 1, but the description contributes no semantics about pagination.

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?

It states a verb (List) and a resource, but the resource is given as the garbled internal name 'seliee_crawl_keyword_analyzer', which is not what the tool name or title say. An agent can infer this enumerates crawl keyword analyzer records, but there is no explanation of what such an entry is or how it differs from get_crawl_keyword_analyzer.

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 and never mentions the closely related get_crawl_keyword_analyzer, create_crawl_keyword_analyzer, or delete_crawl_keyword_analyzer. Nothing indicates this is the enumeration tool versus the single-record tool.

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