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

Annotations already cover the safety profile (read-only, idempotent, non-destructive, closed-world), so the lower bar applies. The description still adds value beyond them by disclosing the return shape: matching guides with a short summary and a flag for whether an interactive practice tool is included, which matters since there is no output schema. It omits ranking/relevance and pagination behavior, keeping it short of a 5.

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 sentences, front-loaded with the verb and resource, then the return shape. No filler, though the long topic enumeration is somewhat list-like and only weakly tied to the pillar parameter.

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 usefully explains what comes back, and all three parameters are at least implicitly addressed. Remaining gaps are minor: result ordering, whether query matches body text or titles only, and how strictly pillar filters.

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 67%: query has an example-bearing description and pillar is an enum with a description. The description's topic list loosely mirrors the pillar enum but never explains the limit cap of 5 or how pillar interacts with query, so it adds little beyond 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 ('Search Yinyang Masters in-depth guides') and enumerates the covered topics, so the domain is unambiguous. It does not contrast itself with adjacent siblings like find_my_crystals or calculate_numerology, which cover overlapping subject matter.

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 implies usage (look up guides on a topic) but gives no explicit when-to-use versus when-to-pick-a-sibling-tool guidance, and no prerequisites or exclusions. An agent must infer that this is the generic content-search entry point while the siblings are computation-specific.

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