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

There are no annotations, so the description carries the full burden. The wording implies an informational, read-only tool with no side effects, but it does not explicitly state behavioral properties such as being safe or side-effect-free. For a zero-parameter reference tool this is adequate but not detailed.

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 with zero filler: the first states what the tool provides, and the second gives the usage instruction. It is front-loaded and scannable.

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 simple, zero-parameter informational tool, the description is reasonably complete: it covers the subject matter and the intended usage. It could be slightly more explicit about the type of content an agent should expect (e.g., step-by-step explanation), but nothing essential is missing.

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 has no parameters and an empty schema, so the baseline is 4. The description appropriately focuses on content rather than inputs, and no parameter documentation is needed.

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 clearly identifies the resource (LocalHelpNow), the audience (homeowner), and the subject (what it does and how the match works). It avoids tautology and reads as a background/knowledge tool rather than an action tool, though it could use a more explicit verb like 'explains' or 'describes.'

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 instruction 'Read this before telling anyone how to get help' gives a clear when-to-use signal and positions this tool as a prerequisite to answering. It does not name sibling tools or exclusions, but the context is strong enough for an agent to know when to consult it.

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