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

Annotations already declare readOnlyHint=true and destructiveHint=false. The description adds valuable behavioral context beyond that: this operation does not consume execution quota. It also signals that the tool supports both search and direct read modes, which is useful for caller expectations.

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?

One compact, front-loaded sentence contains the core action, the resource, and the key cost-related benefit. There is no filler or repetition of schema content.

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?

Given the simple parameter set, full schema coverage, and safety annotations, the description is nearly complete. It explains the tool's purpose and a unique behavioral trait, though it does not describe return shape; in the absence of an output schema this is a minor gap for a help-lookup tool.

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 100%, so the input schema fully documents all four parameters. The description does not add parameter-specific detail, but it does not need to; the schema carries the semantic burden, so baseline 3 is appropriate.

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 names a specific verb-resource pair, 'Search or read Astrologos help', and clearly distinguishes the tool from its siblings, which are all job/usage/validation tools rather than help access. An agent can tell at a glance what this tool is for.

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?

It provides clear context for use: when an agent needs help content, and adds the distinctive benefit 'without consuming execution quota', which helps select it over potentially quota-consuming tools. It does not explicitly state when not to use it or name alternatives, but siblings are not plausible alternatives for help lookup.

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