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. 'List all applications' implies a read-only operation but doesn't disclose behavioral traits like pagination behavior (though hinted by 'page_size' parameter), rate limits, authentication requirements, or what 'all' means in context (e.g., filtered by permissions). It lacks details on return format, error conditions, or side effects.

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, efficient sentence with zero waste. It's front-loaded with the core action and resource, making it easy to parse. Every word earns its place without redundancy or unnecessary elaboration.

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 3 parameters with full schema coverage but no annotations or output schema, the description is minimally complete. It states the action and resource but lacks context on when to use, behavioral details, or output expectations. For a list tool with no annotations, it should provide more guidance on usage and results to be fully helpful.

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 parameters are documented in the schema. The description adds no parameter semantics beyond implying 'all' applications are listed. It doesn't explain how 'include' or 'expand' affect results, or default behaviors. Baseline 3 is appropriate as the schema does the heavy lifting.

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 'List all applications' clearly states the verb ('List') and resource ('applications'), making the purpose immediately understandable. It distinguishes from siblings like 'get_application' (singular retrieval) and 'create_application' (creation), though it doesn't explicitly differentiate from other list tools like 'list_projects' or 'list_users' beyond the resource name.

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 no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites, appropriate contexts, or comparisons with similar tools like 'get_application' for single retrieval or 'create_application' for creation. The agent must infer usage solely from the tool name and sibling list.

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