twake_search

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

No annotations are provided, so the description must disclose behavioral traits on its own. It only says 'Search' and doesn't mention whether the operation is read-only, how results are returned, whether pagination exists, or what permissions are required.

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 repetition or fluff. It states the action, target, and scope efficientlly.

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 1-parameter search tool with no output schema, the description is mostly sufficient: it tells an agent what to call and what the query means. The main gap, result behavior, is minor for this low-complexity tool.

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 already covers 100% of the single parameter with 'Search query'. The description adds no extra meaning about query syntax, matching behavior, or result filtering, so it doesn't improve on 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?

Description has a clear verb ('Search'), a specific resource ('all Twake services'), and omits an explicit scope list (chat, mail, drive). It is easy to tell apart from the per-service sibling tools.

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 explains the context: search is cross-service, while siblings are per-service operations. It doesn't explicitly say 'use this instead of X', but the scope makes the intended use clear.

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