framedeck-mcp

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

Annotations declare readOnlyHint=true and openWorldHint=true. The description adds scope context ('across all boards') aligning with openWorldHint, but doesn't disclose search behavior details like case sensitivity, partial matching logic, or result ordering.

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?

Single sentence of seven words with zero redundancy. Information is front-loaded and every word earns its place describing what, how, and where the search operates.

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?

Adequate for a simple read-only search tool with complete input schema, though lacking description of return values or result structure given the absence of an output schema. Could specify what card fields are returned.

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 complete descriptions for both parameters. The description adds minimal semantic value beyond the schema, briefly noting the keyword-based nature of the search without detailing syntax or query construction.

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?

Clear verb ('Search') and resource ('cards') with explicit scope ('across all boards'). The scope distinguishes it from board-specific tools like list_cards, though it doesn't explicitly name sibling alternatives.

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 explicit guidance on when to use this versus list_cards, get_my_cards, or get_card_details. The phrase 'across all boards' implies global scope but doesn't constitute usage guidelines or prerequisites.

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