framedeck-mcp

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

Annotations indicate non-idempotent writes (idempotentHint=false, readOnlyHint=false), but the description adds no behavioral context such as 'each call creates a distinct comment' or whether notifications are triggered.

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 brief single sentence with no redundancy. However, brevity borders on under-specification given the rich sibling tool context that could cause confusion.

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?

Simple 2-parameter tool with complete schema coverage and annotations. Description lacks output semantics (no output schema exists) and domain-specific context, but meets minimum threshold for invocation.

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 100% with both parameters documented. The description adds no syntax guidance beyond the schema (e.g., does not clarify that partial title matching is supported for card_id per the schema). Baseline 3 appropriate.

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 states the core action (add comment) and target (card), but is minimal and borders on tautology ('add_comment' → 'Add a comment'). It does not distinguish from siblings like 'add_checklist_item' or clarify the domain context.

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?

Description provides no guidance on when to use this versus alternatives like 'update_card' (for description changes) or 'log_work'. No prerequisites or exclusion criteria stated.

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