import-trello-getBoards

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

With no annotations, the description bears full responsibility for behavioral disclosure. It states a read operation ('Retrieves') but omits details like authentication requirements, rate limits, or whether the data is paginated. Minimal transparency.

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?

Extremely concise (one sentence plus a tag), which is efficient for a parameterless tool. However, the brevity sacrifices detail that could be included without adding length, such as expected return format or integration context.

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 no output schema, no annotations, and a simple description, the tool is poorly contextualized. It does not explain the Trello integration, how results are returned, or how this step fits into a workflow like importing boards.

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?

No parameters exist, so the schema trivially covers 100%. The description adds no parameter info but also does not need to. It is minimally sufficient, though it could clarify what 'all boards' means in context.

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 ('Retrieves') and resource ('all boards from Trello'), clearly stating the tool's function. The name includes 'import-trello' to differentiate from other board-related tools like 'board-all', making its niche obvious.

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?

No guidance on when to use this tool versus alternatives (e.g., 'board-all' or 'import-trello-importBoards'). It does not mention prerequisites, conditions, or when not to use it, leaving the agent without decision-making context.

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