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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so safety is covered. The description goes further by disclosing the shape of the return (per-language document counts plus example topics), which annotations cannot convey, though it omits whether the pillar set is fixed or how counts are scoped.

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?

Extremely short and front-loaded: the verb and resource lead, and the returned detail follows immediately. The bilingual duplication restates the same two facts rather than adding one, so it is slightly redundant but costs little.

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, the description carries the return-value burden and partly discharges it by naming document counts and example topics. For a zero-param, read-only listing tool this is close to sufficient, missing only the pillar-set stability and count scoping.

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 takes zero parameters, so there is nothing for the description to document; baseline 4 applies. The schema is an empty object, consistent with the description's stateless listing behavior.

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 ('the 9 pillars') and even specifies the payload (document counts per language, example topics). The resource is distinct enough from siblings wisdom_get_doc and wisdom_search that the agent can tell them apart, though the description never explicitly contrasts itself with them.

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?

Usage is only implied: a zero-parameter listing tool that returns counts and topics reads as a discovery/browsing entry point preceding wisdom_search or wisdom_get_doc. It never says when to prefer this over the siblings or what prerequisites exist.

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