get_readingReturn Cameron's reading list — books currently reading, finished, or abandoned, with notes. Filter by status if given.
| Name | Required | Description | Default |
|---|---|---|---|
| status | No |
| Name | Required | Description | Default |
|---|---|---|---|
| url | Yes | ||
| books | Yes |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description fully carries the burden of behavioral disclosure. It reveals that the tool returns a reading list including statuses and notes, and that filtering is possible. This is a read-only operation with no side effects, and the description sufficiently conveys its behavior.
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, front-loaded sentence that efficiently conveys purpose and filtering. Every phrase contributes value, with no redundant or filler content.
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 (one optional parameter) and the presence of an output schema defining return values, the description is complete. It covers the tool's purpose, scope, and filtering behavior, leaving no significant gaps for an agent to invoke it correctly.
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 schema has one parameter 'status' with an enum but no property description (0% coverage). The description compensates by explaining the purpose: 'Filter by status if given' and by listing the statuses in the main text, adding semantic meaning beyond the raw 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?
The description clearly states the tool's function: 'Return Cameron's reading list' with specific statuses (reading, finished, abandoned) and notes. This differentiates it from sibling tools like get_about or get_now which target different resources.
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 clear context for when to use this tool: to retrieve Cameron's reading list, with optional status filtering. It does not explicitly mention alternatives, but the sibling tools are evidently for different content types, so the context is sufficient without exclusions.
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 (about, now, post, project, pulse, reading, posts, projects, search results, contact, newsletter) and action (get, list, search, submit, subscribe). The two search tools explicitly differentiate by exact substring vs semantic vector search, removing any ambiguity.
All tool names follow a consistent verb_noun snake_case pattern: get_* for single item retrieval, list_* for collections, search_* for search, and submit_*/subscribe_* for actions. No mixed conventions or style deviations.
With 12 tools, the server is well-scoped for a portfolio site. It covers content access (posts, projects, reading), personal info (about, now), live stats, search, and user interactions (contact, newsletter) without being bloated or sparse.
The tool surface fully covers the public-facing domain of a portfolio site: all content types are retrievable in both list and detail forms, search is provided via two complementary methods, and transactional actions for contact and newsletter subscription are included. No obvious gaps or dead ends exist for the intended read-oriented purpose.