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

Annotations already declare readOnly, idempotent, non-destructive and closed-world. The description adds genuinely new behavioral context: reads are 'effective', returning the default when a value is unset (lazy), and it describes the return shape ({ key: value }). That is meaningful beyond the annotation set.

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?

Three tight clauses in one sentence, front-loaded with the verb and resource, then behavior, then return shape. No padding 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?

No output schema exists, and the description compensates by describing the returned { key: value } object(s), plus the effective/default semantics. The main gap is the absence of a pointer to get_board_settings_schema for discovering valid keys.

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 100%, and the schema already documents both parameters including the 'omit to read all' behavior and an example key. The description's 'stored value or default when unset' framing adds mild semantic value but no syntax or key-naming detail beyond the schema, so the 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?

States a specific verb ('read') and resource ('a board's effective settings') and explains the effective-value semantics (stored value or lazy default). It does not distinguish itself from adjacent siblings such as get_board_settings_schema or set_board_setting, so it falls 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?

The description gives per-parameter usage ('Pass a key to read one setting; omit it to read all'), which is helpful, but it never says when to prefer this over get_board_settings_schema (to discover keys) or set_board_setting. Usage context is implied rather than stated.

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