framedeck-mcp

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

While annotations declare readOnly=false and idempotent=false, the description doesn't explain the non-idempotent toggle behavior (especially when 'checked' is omitted) or partial matching risks. It adds minimal behavioral context beyond what annotations and schema provide.

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 at 7 words. Front-loaded with action verbs, but potentially too minimal for a mutation tool—leaves no room for behavioral nuances or warnings about partial matching.

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?

Inadequate for a mutation tool with partial matching logic. Fails to address failure modes (item not found, multiple matches), doesn't clarify the idempotent=false implication, and omits output expectations despite having no output schema.

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?

With 100% schema coverage, the description serves baseline documentation. It maps 'Check or uncheck' to the checked parameter and 'subtask/checklist item' to item_text, but doesn't add syntax details, format constraints, or explain the partial matching semantics beyond the schema.

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?

States specific action ('Check or uncheck') and target resource ('subtask/checklist item'). However, it fails to distinguish from sibling 'add_checklist_item'—both mention checklist items but one creates while this modifies state.

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?

Provides no guidance on when to use this tool versus alternatives, nor does it mention the partial matching behavior implied by the schema. No mention of prerequisites like card existence or handling multiple matching items.

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