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

With no annotations, the description carries the full disclosure burden. It does disclose meaningful behavior: only public profiles are returned, output is limited to bommel.bot records and links, and the empty-query case returns recent people. It omits pagination, result limits, and any auth/permission context, so it is partially but not fully transparent.

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?

The description is short and front-loads the resource, which is good. But the trailing disclaimer ('Not advice, not a recommendation, not an invitation to act') triples the same idea and adds little for tool selection, so it is not as tight as it could be.

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 single-optional-param read tool with no annotations and no output schema, the description covers purpose, scope, and the empty-query behavior reasonably. It still leaves return shape (fields, pagination, result count) and the non-empty query semantics unspecified, so it is only adequate.

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?

There is one optional parameter with 0% schema description coverage, so the description must compensate. 'Empty query lists recent people' explains the no-argument case, but it never says what a non-empty query does (presumably name/keyword matching), leaving the parameter's semantics half-defined.

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 phrase 'Who is on bommel.bot' conveys the resource being listed (people/profiles on the site), and 'Returns factual public records and links' confirms it is a listing/retrieval tool. However, there is no explicit verb and no differentiation from nearby siblings like list_talk or search_feed, so an agent cannot fully tell it apart by description alone.

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 hints at query behavior ('Empty query lists recent people') but never states when this tool should be chosen over explore_hive, search_feed, or list_talk. There are no exclusions, prerequisites, or alternative-routing guidance.

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