get_help

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

With no annotations provided, the description must fully disclose behavioral traits. However, it only states 'Show tool documentation' without mentioning whether the operation is read-only, requires authentication, or has any side effects. This is insufficient for an agent to understand the tool's behavior.

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 extremely short (three words), but this is underspecification rather than good conciseness. It lacks structure and fails to convey essential information. Every sentence should earn its place, but here the single sentence is too vague to be useful.

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 tool's simplicity (one optional parameter) and the presence of an output schema, the description still falls short. It does not explain the purpose of the 'tool' parameter, what the output contains, or how to use the tool effectively. The description is incomplete for an agent to invoke it correctly.

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 one parameter 'tool' with no description (0% coverage). The description does not mention or explain this parameter. It fails to add meaning beyond the schema, leaving the agent unaware that the 'tool' parameter specifies which tool's documentation to show.

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 'Show tool documentation' clearly states the tool's purpose: it displays documentation about tools. This distinguishes it from sibling tools that retrieve specific data (e.g., jobs, profiles). The verb 'show' is specific and the resource 'tool documentation' is unambiguous.

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 no guidance on when to use this tool versus alternatives. It does not specify that it should be used when the agent needs help with a particular tool, nor does it mention any exclusions or prerequisites. The agent has no context for appropriate use.

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