framedeck-mcp

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

Annotations indicate read-only and potential external access (openWorldHint). Description adds valuable content disclosure beyond annotations by specifying exactly what data structures are returned (stages, counts, overdue items) to compensate for missing output schema. No contradiction with readOnlyHint.

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 efficient clauses with zero waste. Front-loaded with the core action and return value, followed by parameter default behavior. Every word earns its place—'quick overview,' 'stages,' 'overdue items' all convey specific semantics.

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 lack of output schema, the description adequately discloses the return structure (stages, counts, overdue status). Tool is simple (1 optional param) with clear annotations; description sufficiently covers the behavioral contract without redundancy.

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%, so baseline applies. The description's 'Uses active board if not specified' largely restates the schema's '(uses active board if omitted)' without adding new constraints, format details, or examples beyond the structured description.

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?

Description states specific action ('Get a quick overview'), resource ('board'), and detailed scope ('stages with card counts, overdue items'). Clearly distinguishes from sibling tools like get_card_details (specific card) or list_cards (flat list) by emphasizing summary/aggregated nature.

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 clear context that this returns a high-level snapshot ('quick overview') rather than detailed data. Explicitly documents the default behavior ('Uses active board if not specified'), guiding invocation when the optional parameter is omitted. Lacks explicit naming of alternatives for detailed queries.

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