Get the stories (examples/snippets) for a specific EOxElements custom element. This includes descriptions and vanilla JS code snippets.
| Name | Required | Description | Default |
|---|---|---|---|
| tagName | Yes | The tag name of the element. |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden. It discloses that the tool returns descriptions and vanilla JS code snippets, adding some context beyond the name. However, it does not mention return format, potential errors, or read-only behavior, leaving some ambiguity for a tool with no annotation safety hints.
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 concise two-sentence structure with the key action front-loaded ('Get the stories'), followed by a clarifying detail. No filler or redundant 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?
The tool is simple with one parameter and no output schema. The description adequately explains what the result includes (descriptions and code snippets) and clarifies the ambiguous term 'stories.' It lacks explicit return structure and error handling, but for a straightforward getter this is a minor gap.
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 input schema has 100% description coverage with a straightforward tagName parameter. The description only restates that it is for a specific element, adding no additional semantic value beyond the schema's 'The tag name of the element.' Baseline 3 is appropriate.
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 uses the specific verb 'Get' with the resource 'stories (examples/snippets)' for an EOxElements custom element, clearly distinguishing it from sibling getters such as get_element_attributes or get_element_methods. It also adds useful specifics about content (descriptions and vanilla JS code snippets).
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 implies usage for retrieving examples/snippets but does not explicitly state when to use this tool versus siblings or provide exclusions. The context is clear enough for an agent to infer its use from the element aspect (stories), but no direct guidance is given.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Each tool targets a distinct aspect of an EOxElements custom element (attributes, CSS parts, CSS properties, events, methods, properties, slots, stories), making selection unambiguous. Even get_element_details, which might aggregate information, is clearly named as a full-details option rather than overlapping with the specific aspect getters.
All tools follow a consistent get_element_<aspect> pattern, with list_elements as the sole exception, which still uses a verb_noun structure. This uniformity makes the toolset highly predictable and easy to navigate.
With 10 tools, the server is well-scoped for the purpose of exploring EOxElements custom elements. Each tool covers a specific documented aspect, and the count fits comfortably within the ideal 3-15 range.
The toolset comprehensively covers the public API surface of a custom element library: listing elements and retrieving all standard web component facets (attributes, properties, methods, events, slots, CSS parts, CSS properties) plus stories and full details. No obvious gaps exist for the documentation purpose.
