kakao_search

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

The annotations only declare readOnlyHint and openWorldHint, so the description carries the burden of explaining behavior. It adds valuable details: newest-first ordering, cursor-based pagination, result fields, and the text-only matching limitation. No contradictions with annotations.

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 short sentences, each earning its place: the first defines scope and ordering, the second covers result fields and pagination, the third explains a critical limitation and alternative. The most decision-relevant information is front-loaded.

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 a 100%-documented schema, an output schema, and read-only annotations, the description supplies all the behavioral context an agent needs: ordering, pagination, return fields, and exclusion of media. Nothing essential is missing for correct invocation.

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%, so the baseline is 3. The description adds useful cross-parameter meaning by explaining how `before` relates to `next_cursor` for pagination and how the search scope can be narrowed to a single chat via `chat_id`. This goes slightly beyond the schema's individual parameter descriptions.

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 opens with a specific verb and resource: 'Search message text across chats (or in one chat)', and adds the ordering behavior 'newest matches first'. It also names the included result fields, making it easy to distinguish from sibling tools like kakao_read_messages and kakao_list_chats.

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?

It explicitly routes media-related searches away from this tool to kakao_read_messages with since/until, and gives precise pagination instructions ('pass before=<next_cursor> until next_cursor is null'). This gives an agent clear when-to-use and when-not-to-use guidance.

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