List Connor Gallic's original blog posts on AI automation, voice AI, programmatic SEO, and running products solo. Optional filters: query (matches title/excerpt) and category.
| Name | Required | Description | Default |
|---|---|---|---|
| query | No | Free-text filter over title and excerpt. | |
| category | No | Filter by category, e.g. "AI Automation" or "SEO Strategy". |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations provided, so description bears full burden. It implies a read operation but does not explicitly state non-destructive behavior, authentication needs, or result 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?
Two concise sentences with front-loaded purpose, no unnecessary 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?
Covers the core function and filter options. Lacks mention of output format or pagination, but acceptable for a simple list tool with no output schema.
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% with descriptions. The description adds minimal extra value (e.g., 'matches title/excerpt'), not significantly beyond the schema.
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?
Description clearly specifies the action (list), resource (original blog posts), and domain (AI automation, etc.), distinguishing it from sibling tools like list_products and get_post.
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?
States optional filters (query, category), implying usage for filtered listing. Lacks explicit when-not or alternative tool references, but is clear enough for typical use.
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: catalog overview, personal profile, single blog post, products list, reading log, writing list, and action recommendation. No apparent overlap or ambiguity.
All tool names follow a consistent 'verb_noun' pattern with 'get', 'list', and 'recommend' verbs, making it predictable and easy to understand.
Seven tools is ideal for this personal portfolio server, covering profile, products, blog, reading log, and a recommendation action without being too sparse or overwhelming.
The tool surface covers the main aspects of the personal brand: profile, products, writing, reading log, and a recommendation. A minor gap is the lack of a tool to list all categories or tags, but filters partially address this.
