kupid_lms_get_board_post

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

The description discloses that attachments have time-limited URLs and explains how to download files via file_id. It covers the main behaviors beyond the schema, though no annotations exist.

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?

Description is concise, well-structured with paragraphs and clear Args list. Every sentence adds value without redundancy.

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?

Tool has 3 required params and an output schema. The description covers the result contents and file download process sufficiently. Could mention that the tool is read-only for completeness.

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 explains each parameter in Args, but only provides minimal context (e.g., post_id is from list endpoint). Schema coverage is 0%, so the description does not add much beyond naming.

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 post details, attachments, and comments, distinguishing it from sibling tools like kupid_lms_list_board_posts which lists posts.

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?

No explicit when-to-use or alternatives are given, but it's implied from the context that this tool is for getting a single post's full details. Lacks guidance on when not to use it.

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