listMiroBoards

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

No annotations are provided, so the description must carry the burden. It discloses that results are scoped to the authenticated user, which is useful. However, it does not mention pagination, ordering, or that this is a read-only operation (though 'Retrieves' implies safety). It lacks details about potential errors or limits, so transparency is adequate but not rich.

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 a single, concise sentence that is front-loaded with the action and resource. Every word contributes meaning, with no redundant phrasing. It is appropriately sized for the tool's simplicity.

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?

For a simple list tool with no parameters and no output schema, the description provides enough context: it specifies the resource (Miro boards) and the user scope. It does not explain the structure of each board, but that is typically implied by the service domain. The lack of annotations is partially compensated by the straightforward nature of the operation.

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?

The tool has zero parameters, and the schema is empty, so the description does not need to explain parameter semantics. The baseline for zero-parameter tools is 4, and the description adds no unnecessary detail about inputs.

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 the tool retrieves a list of boards for the authenticated user. The verb 'Retrieves' is specific, and the resource is 'list of boards', which distinguishes it from sibling Miro tools like getMiroBoard (single board) and postMiroNote (creates a note).

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 implies usage by saying 'list of boards', but it does not explicitly state when to use this tool versus alternatives like getMiroBoard. There is no mention of scenarios where listing all boards is needed, nor any exclusion of cases where a specific board should be fetched. Usage context is clear but not directly contrasted with siblings.

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