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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It explicitly mentions 'Free, no API key' (covering authentication and cost) and describes the return format as a TSV catalog with exact column names. It stops short of declaring read-only behavior, but for a help/catalog tool that returns no content, 'get_help' strongly implies no side effects. Given a complex schema, this is a reasonably transparent description.

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 highly concise: four short sentences (or clauses) packing essential information: free/no key, output format, order-of-call, and a resource preference. It is front-loaded with the 'call first' instruction and the TSV specification, and there is no filler material.

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 zero-parameter tool with no output schema, the description supplies all necessary context: what it does (returns usage and catalog), how to invoke it (call first), and how to access the same data differently (botkelp://catalog). The TSV field list gives a full expectation of return structure. No critical information appears missing for a help entry point.

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 input schema has zero parameters, and the baseline for such a tool is 4. The description adds no parameter-specific meaning because there are none, correctly focusing instead on what the tool returns. No further parameter compensation 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 a specific purpose: providing usage instructions and the full component catalog in a defined TSV format with explicit fields (id, name, version, description, provides, requires, conflictsWith). It also positions itself as the entry point ('Call this first'), distinguishing it from sibling get_* tools that fetch individual components or settings.

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 contains explicit usage guidance: 'Call this first' tells the agent when to invoke the tool, and 'Prefer resource botkelp://catalog if your client supports it' gives an alternative route. However, it does not provide a when-not-to-use condition or explain when to use sibling get_component/get_projects tools instead, although the 'first' instruction implies those tools come after.

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