search_api_docs

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

The annotation readOnlyHint=true already establishes the safe read-only nature of the operation. The description adds that it searches 'included' documentation and should be read before coding, but does not disclose search behavior such as result format, matching, or limits. It adds some value beyond the annotation without contradicting it.

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 two concise sentences, front-loaded with the core action and followed by a usage directive. Every word earns its place with no redundancy or filler.

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 simple one-parameter tool with an output schema, the description adequately covers scope ('included' docs) and usage timing ('before writing code'). It does not detail the return value, but the presence of an output schema shifts that burden, and the description is sufficient for an agent to understand the tool's role.

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 provides only a 'query' string with zero description coverage. The description implies 'query' is the search phrase, but provides no syntax, formatting, or examples. Since the schema gives no guidance and the description only trivially defines the parameter, the description fails to meaningfully compensate for the missing schema documentation.

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 a specific verb ('search') and resource ('included Blender API documentation'), making the tool's purpose unambiguous. However, it does not differentiate from the sibling tool get_python_api_docs, which may also provide API documentation access.

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?

'Baca SEBELUM menulis kode' explicitly instructs when to use this tool (before writing code), providing clear contextual timing. It does not mention alternatives or exclusions, but the guidance is direct and actionable.

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