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

Annotations only carry readOnlyHint, and the description adds substantial beyond-annotation context: the exact content scope, an explicit exclusion ('private work-session cards and session metadata are never returned'), and a semantic caveat that 'issue assignment does not prove a development stage'. This is exactly the kind of behavioral disclosure that helps an agent interpret results.

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?

Front-loads the core purpose, then layers scope, filter semantics, and caveats in dense but non-redundant sentences. Every sentence carries a distinct fact; nothing restates the name or title.

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?

With no output schema, the description does the work of explaining return contents and exclusions, and the readOnly annotation covers safety. It omits ordering, pagination, or result limits, which is a minor gap for a list tool but not blocking.

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 coverage is 0%, so the description must compensate, and it does for person_user_id ('filters by assignee only, not creator' – a non-obvious distinction). project_id is only implied via 'one joined shared project', leaving its UUID nature undocumented, but the name is largely self-explanatory.

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?

States a specific verb and resource ('Read one joined shared project's work board') and immediately enumerates the contents (shared cases, linked to-dos/GitHub Issues, unlinked to-dos, snapshots). The word 'one' distinguishes it from the sibling list_all_shared_project_work_boards, so an agent can route without opening either schema.

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?

Implies the correct context via 'one joined shared project' (a precondition: the project must be joined) and clarifies the assignee-only filter, but never names the alternative list_all_shared_project_work_boards or states when-not to use this tool. Clear context, no explicit exclusions.

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