update_board_context

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

With no annotations provided, the description carries the full behavioral burden, and it does disclose one important trait: omitted fields are left unchanged (PATCH semantics rather than replace). It does not say whether supplying 'context' replaces the entire existing markdown, what permissions are required, or what the response looks like.

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 sentences, front-loaded with the mutation target and followed by the partial-update caveat. Nothing is redundant or padded.

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 three-parameter mutation with no annotations and no output schema, the description covers the essential partial-update semantics but omits whether writes overwrite existing values, permission requirements, and confirmation/return behavior. Adequate but with clear gaps.

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 100%, so the schema already documents boardId, context (markdown), and repository (Git URL) in detail. The description adds only the 'and/or' optionality note, which is largely inferable from the schema's non-required fields, so baseline 3 applies.

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 states a specific verb ('Set') and resource ('a board's project context ... and/or repository URL'), so an agent immediately knows what the tool mutates. It does not need to distinguish itself from siblings, since no other listed tool touches board-level context.

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?

Usage is only implied: the wording makes clear it is for writing board context/repository, but there is no explicit when-to-use statement, no prerequisites, and no named alternative (none exists among the siblings). 'Omitted fields are left unchanged' hints at partial-update use but reads as behavior, not guidance.

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