board-all

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

No annotations are provided, so the description carries full burden. It does not disclose behavioral traits such as authentication requirements, rate limits, pagination, or default filtering behavior (e.g., whether archived boards are included by default or how the 'type' and 'archived' filters affect results). The phrase 'all boards' may be misleading given optional filters.

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 very concise (one sentence plus a tag). It is front-loaded with the core purpose. However, it lacks structure such as parameter listings or usage notes. The tag is redundant but harmless.

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?

Given the tool has 3 parameters, no output schema, and no annotations, the description is incomplete. It does not explain optional filters, default behavior, return format, or distinguish adequately from sibling tools. An agent would lack key information to use this tool correctly.

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%. The description only implies 'workspacePublicId' via 'for a given workspace', but does not mention the optional parameters 'type' (enum) or 'archived' (boolean). It adds minimal meaning beyond the schema, failing to explain valid values or how filters modify the result set.

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 clearly states 'Retrieves all boards for a given workspace', specifying the verb (retrieves), resource (boards), and scope (for a given workspace). It distinguishes from sibling tools like board-byId and board-bySlug which retrieve single boards, and board-create/update/delete which mutate boards.

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 usage is implied by the description: use this tool when you need a list of all boards in a workspace. However, there is no explicit guidance on when not to use it or what alternatives exist (e.g., board-byId for specific boards). The description relies on the agent inferring from the purpose.

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