read_board_notes

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

With no annotations, the description carries the full disclosure burden but does add real behavioral facts: unread-only filtering is the default, and the call can optionally mutate state by marking notes read. It says nothing about permissions, what "blackboard" scopes to, or whether marking read is reversible/lasting.

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?

One sentence, front-loaded with the action and resource, followed by the two behavioral clauses. No filler or 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?

An output schema exists so return values need not be described, and the default/mutation behavior is covered. However, for a 5-parameter tool with zero schema descriptions, the absence of any explanation for topic and target leaves the invocation contract incomplete.

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% and there are 5 parameters, so the description must compensate. It names the project scoping and both boolean behaviors (unread_only default true, mark_as_read optional), but never mentions the topic or target parameters, leaving two of five parameters unexplained anywhere.

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 gives a specific verb+resource ("Read blackboard notes for a project") plus the default scoping behavior, so an agent can distinguish it from write/delete siblings like post_board_note and clear_board_notes. It does not explicitly name a sibling or contrast itself with one, which keeps it short of a 5.

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 explicit when-to-use guidance and no mention of alternatives (e.g., post_board_note for writing, clear_board_notes for deletion). Usage is only implied by the word "Read" and by the stated default of unread-only notes.

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