kupid_lms_list_board_posts

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

With no annotations, the description must disclose behavioral traits. It states the tool retrieves a list but does not mention pagination behavior, ordering, or whether it is read-only. The 'page' parameter implies pagination, but no limits or defaults beyond the default value are discussed.

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 concise, with a clear main sentence followed by parameter explanations. It is front-loaded with the purpose. However, it could be more structured (e.g., separate the parameter descriptions into a table or bullet list for easier parsing).

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?

The description covers all four parameters with clear meanings and relates board_id to another tool. It also explains keyword is for title search. However, it lacks information on result ordering, maximum results per page, or any filtering options beyond keyword. Given the presence of an output schema, return values are not needed, but behavioral context is missing.

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 description adds meaningful semantics beyond the input schema: it explains that board_id comes from kupid_lms_list_boards, page defaults to 1, keyword defaults to empty. This compensates for the 0% schema description coverage. However, it could provide more detail on acceptable values or formats.

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 tool retrieves a list of posts from a board (게시판의 게시글 목록을 조회합니다). It specifies the resource (board posts) and action (list). Among siblings, 'kupid_lms_get_board_post' retrieves a single post, so this tool is distinct.

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 parameter descriptions but no explicit guidance on when to use this tool versus alternatives. It does not mention when not to use it or any prerequisites. For example, it doesn't reference that this is for listing all posts in a board, while 'kupid_lms_get_board_post' is for a single post.

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