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

The readOnlyHint annotation already signals safety, and the description adds behavioral detail without contradicting it. It transparently enumerates what the help response includes: refusals, access limits, provenance fields, recommended next calls, and the interaction contract. It does not mention its own operational limits, but the read-only nature lowers the burden.

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 dense but efficiently structured: first sentence defines the core purpose, second lists the returned contents, third gives a direct usage pointer. It is not overly long for the rich information it conveys, though the second sentence is a long list that could arguably be split for readability.

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 one-parameter, read-only help tool with no output schema, the description is thorough. It spells out the output categories, the prerequisite tools/list discovery step, and the recommended invocation timing. The agent gets enough context to understand what the tool returns and how to call it successfully.

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 already provides 100% coverage for tool_name, including the instruction 'Exact tool name from tools/list.' The description reinforces this by saying to discover names via tools/list, but it adds no new parameter syntax or format details. With full schema coverage, 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 states a specific verb+resource: 'get tool help' / 'guidance for one tool visible on this MCP facade.' It clearly differentiates from siblings like get_catalog and query_dataset by focusing on meta-guidance rather than data retrieval. The list of returned content (when to use, refusals, example, limits) makes the function unmistakable.

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 provides explicit usage context: 'Use tools/list to discover names, then call this before an unfamiliar tool.' This is a clear when-to-use directive. It doesn't explicitly mention when-not-to-use or compare with sibling tools, but the workflow is unambiguous and actionable.

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