get_help

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

No annotations are provided, so the description carries the full burden. It only states the basic action without disclosing the return format, whether it is a read-only operation implicitly, or any side effects. The description is too sparse to inform an agent about expected outcomes or constraints.

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 a single sentence with no redundant words. It is front-loaded with the verb and noun. While extremely brief, it is concise and does not waste any space. The structure is appropriate for the minimal information it provides.

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 (1 parameter, no output schema), the description is incomplete. It lacks any details about the expected search term format, the nature of the returned documentation, or how to interpret results. An agent would not have enough information to use the tool correctly without additional assumptions.

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 schema describes a single parameter 'search_term' with no description, and the schema description coverage is 0%. The tool description does not explain what should be placed in 'search_term' or how it is used. The description adds no semantic value beyond the raw type 'string', so an agent cannot infer appropriate input.

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 states the verb 'gets' and the resource 'Godot documentation', making the tool's purpose unambiguous. None of the sibling tools relate to documentation, so it is naturally distinct. However, it does not elaborate on what kind of documentation or how results are returned, leaving some ambiguity.

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?

There is no guidance on when to use this tool versus alternatives. While no sibling tool appears to serve the same purpose, the description does not explicitly say 'use this when you need to look up Godot documentation'. An agent is left to infer usage from the name and minimal description.

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