Kanban Board Statistics

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

Annotations already declare readOnlyHint and idempotentHint; description reinforces 'Read-only' and adds context about vault session vs explicit path. No contradictions.

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?

Two paragraphs with no fluff. First sentence front-loads purpose. Second paragraph adds vault context. Every sentence adds value.

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 simple nature, presence of output schema, and rich annotations, the description provides all necessary context: purpose, differentiation, usage guidance, and vault behavior.

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 50% due to missing vaultPath description, but the description explains vaultPath's role (override session vault). filePath description is minimal but adequate. Compensates partially for coverage gap.

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 it summarizes a Kanban board with specific statistics (total cards, completed, incomplete, rate, per-column breakdown) and distinguishes itself from sibling kanban.parse by noting it's for when you don't need full card content.

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?

Explicitly tells when to use (dashboards, progress checks) and when not (use kanban.parse for card content). Also explains vault path behavior with precedence rules.

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