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

The annotations already establish that this is a safe read-only, non-destructive, closed-world operation. The description adds useful behavioral context with 'fixed' and 'No scores', but it does not describe ordering, pagination, or the exact response shape.

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?

The description is two short sentences and front-loads the core action and scope. It is efficient, though the phrase 'fixed buyer questions' could be slightly clearer about what is being returned.

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?

This is a simple read-only tool with one optional parameter and no output schema, and the annotations already cover safety behavior. The description is adequate for calling it correctly, though it could say more about what a question object contains beyond the absence of scores.

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 category parameter and its enum values are already documented. The description restates that questions can be scoped to a board or retrieved for every question, but it does not add syntax or clarify the mismatch between the parameter name 'category' and its schema description 'Board id'.

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 uses a specific verb and resource: list fixed buyer questions on a board or every question. It clearly distinguishes the all-questions mode from the board-scoped mode, though it does not explicitly differentiate itself from siblings such as get_question or list_categories.

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 phrase 'on a board, or every question' implies that omitting the category parameter lists all questions, matching the schema. However, it gives no explicit guidance on when to use this instead of get_question, get_category_board, or list_categories.

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