acedatacloud_search_docs

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

No annotations are provided, so the description must carry the full burden. It mentions 'No token required', which is a helpful behavioral detail about authentication. However, it does not disclose any potential side effects, rate limits, or other traits beyond what is already implied by the action.

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?

Three sentences totalling 21 words. Every word adds value. The description is front-loaded with the action and immediately gives key details. Perfect conciseness.

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 low complexity (2 parameters, simple search), the description covers the main purpose, return fields, and authentication. It does not mention pagination or error handling, but with an output schema likely covering return structure, this is adequate. Score reflects minor gaps.

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?

Schema coverage is 100%, and the description does not add any additional meaning beyond the schema's parameter descriptions. The mention of 'No token required' is about authentication, not parameter semantics. Therefore, baseline score of 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 'Full-text search the AceDataCloud documentation' with a specific verb and resource. It also lists the return fields, clearly distinguishing it from sibling tools like acedatacloud_list_docs (listing all docs) and acedatacloud_get_doc (retrieving a single doc by ID).

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 clear context that this tool is for full-text search, but does not explicitly state when to use it versus sibling search tools or list tools. However, the name and purpose make it fairly clear that it is for searching rather than listing or retrieving.

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