SD Elements MCP Server

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

No annotations are provided, so the description carries full burden. It mentions the tool makes 'generic API requests' but doesn't disclose important behavioral traits like authentication requirements, rate limits, error handling, or response formats. The description adds some context about when to use it but lacks operational details needed for a mutation-capable tool.

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 perfectly concise with two sentences that each earn their place: the first states the purpose, the second provides critical usage guidelines. It's front-loaded with the core functionality and wastes no words.

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 this is a generic API tool with 4 parameters, no annotations, and no output schema, the description is incomplete. While it excels at purpose and guidelines, it lacks information about authentication, error handling, response formats, and other operational context needed for a tool that can perform any HTTP operation.

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%, so the schema already documents all 4 parameters thoroughly. The description doesn't add any parameter-specific information beyond what's in the schema. It mentions HTTP methods and endpoints generally but provides no additional syntax, format, or semantic details about the parameters.

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's purpose as 'Make a generic API request to a custom endpoint' with specific verbs (GET/POST/PUT/DELETE) and distinguishes it from sibling tools by explicitly naming 'get_project' as an alternative for specific operations. It provides both what it does and what it doesn't do.

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 usage guidance with 'Use when user says...' examples and clear exclusions: 'Do NOT use for specific operations - use dedicated tools like get_project instead.' It directly addresses when to use this tool versus alternatives among the many sibling tools.

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