get_blog_postFetch a single SCA Zandomeni blog article by slug. Returns title, description, canonical URL and article text.
| Name | Required | Description | Default |
|---|---|---|---|
| slug | Yes | Article slug (the part after /blog/ in the URL). | |
| maxChars | No | Max characters of article text to return. |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The annotations already declare readOnlyHint, openWorldHint, and idempotentHint, which cover the safety profile. The description adds the concrete return payload (title, description, canonical URL, article text), which is behavioral detail beyond what the annotations provide. No contradiction exists, and the added return fields help the agent anticipate the output format.
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, compact sentence that front-loads the action, resource, and identifying criterion, and ends with the return fields. Every word earns its place, with no redundancy or fluff.
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 tool's simplicity—two parameters, one required, no output schema—the description covers the core purpose, the return payload, and the lookup mechanism. The annotations provide the read-only and idempotent context, and the sibling tools clarify the information landscape, so the description is complete enough for a single-fetch 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?
The input schema provides full descriptions for both slug and maxChars with 100% coverage. The description's phrase 'by slug' merely restates what the schema already specifies, and it does not add any additional meaning or constraints for the parameters. Therefore the baseline score 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 uses the specific verb 'Fetch' to identify the action, specifies the resource as a 'single SCA Zandomeni blog article', and adds the key criterion 'by slug'. This clearly distinguishes it from the sibling tool search_blog_posts, which would be used for discovery rather than retrieval.
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 that the tool is used when a slug is already known, but it does not explicitly state when to use this tool versus alternatives like search_blog_posts. The guidance is implied by the 'by slug' phrase rather than explicitly stated, so it falls short of clear when-to-use and when-not-to-use instructions.
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 has a clearly distinct purpose: retrieving a blog post, getting contact info, listing expertise areas, and searching blog posts. There is no overlap or ambiguity between them.
All tool names follow a consistent verb_noun snake_case pattern: get_blog_post, get_contact_info, list_expertise_areas, search_blog_posts. This makes the API predictable and easy to navigate.
With 4 tools, the server is well-scoped for its purpose of providing firm information and blog access. Each tool earns its place and the count is within the ideal range.
The core functionality is covered: blog search/retrieval, expertise areas, and contact info. Minor gaps exist such as no tool for firm history or team details, but these are not critical for the server's apparent purpose.