help

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

Annotations already provide readOnlyHint, idempotentHint, and non-destructive traits. The description adds further behavioral context beyond that by explaining that the tool returns complete documentation and action lists, and that it can suggest close tool names for misspellings. No hidden or surprising behavior is apparent.

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 functional and direct, but it repeats the entire 46-item enum that already exists in the schema. While the list makes the scope obvious, it adds length without adding value for an agent that already has schema access. Structurally it is readable but somewhat redundant.

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 full enum coverage in the schema, the description is largely complete. It explains the purpose, expected input, what information will be returned, and one useful edge behavior. Lacking an output schema is negligible here because the output is itself documentation for other tools.

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 parameter schema already fully defines tool_name with type, description, and an enum of all 46 allowed values. The description adds only a brief restatement of '传 tool_name 获取该工具的详细用法、参数、action 列表', which is useful but does not meaningfully extend per-parameter semantics beyond the schema.

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 action and resource: '获取完整文档' for any tool, and lists accepted tool names. It is not a tautology and is informative enough for an agent to understand what help does. It does not explicitly distinguish itself from the similarly naming sibling 'docs', so it falls just short of full sibling differentiation.

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 explicitly tells the agent to pass tool_name and states what will be returned: detailed usage, parameters, and action list. It also notes automatic spelling correction. It does not provide when-not-to-use or alternate tool comparisons, but for a meta help tool the usage context is clear and actionable.

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