memeboat-mcp

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

Given no annotations, the description carries the transparency burden. It discloses that the tool creates a meme, returns specific URLs, and has rate limits. It also explains the caption placement algorithm. While it does not cover authentication or potential mutations beyond creation, the key behavioral traits are addressed.

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?

The description is three sentences, front-loaded with the core action, and each sentence provides distinct value (creation action, placement rules, return values, rate limiting). No extraneous information.

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?

For a tool with no output schema, the description adequately explains return values (URLs). It also covers rate limits and captioning rules. Minor gaps include error handling and the need to first fetch a template via siblings, but these are implied and manageable.

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%, but the description adds value by explaining how the 'texts' parameter is interpreted ('1 caption = bottom text, 2 captions = classic top/bottom, N captions fill...') and suggesting to match 'suggestedCaptionCount'. This goes beyond the schema's property descriptions.

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 the action ('Create a real, shareable meme') and the resource ('on memebo.at'), and it distinguishes from sibling tools (get_meme_template and search_meme_templates) by focusing on creation rather than retrieval. The caption placement rules further clarify the tool's intent.

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?

The description provides explicit guidance on caption ordering ('texts are placed top-to-bottom...') and rate limits ('Rate-limited per IP — space out repeated calls'). However, it does not explicitly state when not to use this tool versus alternatives; the differentiation from siblings is implied through purpose.

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

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

No annotations provided, but the description discloses the tool's read-only nature implicitly and lists the returned fields (dimensions, image URL, caption count). No harmful behaviors are omitted.

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?

The description is a single, well-structured sentence that conveys all necessary information without redundancy or extraneous details.

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?

For a simple retrieval tool with one parameter and no output schema, the description sufficiently explains the tool's purpose, input, and output. Sibling tools are clear.

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?

The description adds meaning beyond the schema by explaining what the slug represents and where to find it. The schema already describes the parameter, but the description enriches it with practical context.

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 explicitly states 'Fetch one meme template by its slug', with a clear verb and resource. It distinguishes itself from siblings by specifying the input source (search_meme_templates or URL).

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?

The description indicates where to obtain the slug (from search_meme_templates or a URL), providing clear context for when to use this tool. It does not explicitly state when not to use it, but the context is sufficient.

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

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

No annotations are provided, so the description carries full burden. It discloses the scope (25,000+ templates), search capability (by name/topic), and return fields (slug, image URL, caption count). While it doesn't explicitly state read-only, the nature of search implies no side effects, which is sufficient.

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 sentences, no redundant information, directly conveys purpose, usage hint, and output. Optimal density for an AI agent.

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 no output schema, the description adequately explains return values (slug, image URL, caption count) and ties it to sibling tool create_meme. Covers all essential aspects for a search tool.

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 description coverage is 100% with clear parameter descriptions. The description adds context about the catalog size and output fields, but does not enhance the meaning of the query or limit parameters beyond what the schema provides. Baseline of 3 applies.

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 the tool searches a catalog of 25,000+ meme templates by name or topic, using a specific verb 'search' and resource 'meme templates'. It differentiates from siblings (create_meme, get_meme_template) by focusing on discovery and providing a slug for subsequent creation.

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?

The description explains the output includes a slug to be used with create_meme, implying usage before creation. However, it does not explicitly state when not to use or mention alternatives like get_meme_template for direct retrieval.

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