list_projectsLists Khalid's shipped case studies (products built at Keyin College) and his side projects (the Lab). Each entry includes a slug usable with get_case_study, a summary, and tags.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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 the output shape: each entry includes a slug usable with get_case_study, a summary, and tags. It does not explicitly state read-only behavior, but 'Lists' and the absence of mutation language make that reasonably clear.
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?
A single sentence front-loads the action and scope, then adds only the essential return details: slug, summary, and tags. Every clause earns its place with no redundant filler.
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?
For a no-parameter list operation, the description is nearly complete: it identifies what is listed and what each entry contains. It does not mention ordering, pagination, or a full return type, but those are not essential given the tool's simplicity and the absence of an 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?
The tool has zero parameters, so the 100% schema coverage makes parameter semantics trivially complete. The 0-parameter baseline applies, and the description correctly says nothing about parameters because there are none.
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 states a specific verb ('Lists') and a precise resource: Khalid's shipped case studies at Keyin College and his side projects (the Lab). This clearly distinguishes the tool from siblings like list_writing, and the mention of get_case_study ties it to a related workflow.
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 when to use the tool—when a caller needs a list of Khalid's projects—but it does not explicitly discuss alternatives or when not to use it. The context is clear enough to infer selection, 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 resource and action: profile, resume, availability, projects, writing, case study detail, post detail, site search, and persona Q&A. The only potentially overlapping pair (list_projects/get_case_study and list_writing/get_post) follows a clear list-then-get pattern, so an agent can easily distinguish them.
Tool names follow a consistent verb_noun pattern: get_*, list_*, ask_khalid, and search_site. All are lowercase with underscores and use clear, predictable verbs that match their purpose.
Nine tools is well-scoped for a personal portfolio server. Each tool covers a meaningful aspect of the site's content or interaction, and none feel redundant or superfluous.
The surface covers the full portfolio experience: profile, resume, availability/contact, project listings with deep dives, writing listings with content retrieval, and whole-site search. No obvious dead ends or missing operations for the stated purpose.