Get board

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=true, so the safety profile is covered. The description adds modest value by disclosing that the payload includes labels and members rather than the bare board record. It does not describe error behavior for an invalid or inaccessible board_id.

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?

Two short lines with the functional summary front-loaded. The trailing REST endpoint is somewhat implementation-level detail but is compact and may aid debugging, so it does not seriously dilute the definition.

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?

There is no output schema, so the description carries some burden for return values; it covers labels and members but not other likely board fields such as title, color, owner, or archived state. For a simple single-resource getter it is minimally sufficient, but an agent cannot anticipate the full response shape.

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 description coverage is 0%, so the single board_id parameter is undocumented in the schema; the description only implies its meaning via the URL template {board_id}. With just one self-evident parameter this is mostly adequate, but no format, source, or acquisition guidance (e.g., from nextcloud_list_boards) is offered.

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?

"Read one board with its labels and members" gives a specific verb plus resource and names what is bundled in the response, which distinguishes it from the sibling nextcloud_list_boards. It does not explicitly call out the list tool as the alternative, but "one board" makes the scope unambiguous.

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?

There is no statement of when to use this versus nextcloud_list_boards, nextcloud_get_card, or nextcloud_list_stacks. The agent must infer from the verb that this is a single-item fetch requiring a known board_id; there are no preconditions or exclusions given.

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