Get content item

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations, the description carries the burden of explaining behavior. It clarifies that this is a read-style fetch returning all fields including body content, but it does not address potential error behavior, authentication, uniqueness of slug/id, or what happens when neither selector is provided.

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, tightly written sentence that front-loads the core action and return scope. Every phrase adds useful information about what is fetched and how it is identified.

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 simple 3-parameter tool, the description covers purpose, resource type, selectors, and return detail. But with no output schema or annotations, it could still add guidance on required inputs and how this tool relates to list_content or other content-fetching siblings.

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 description coverage is 0%, so the description must add parameter meaning. It maps 'blog post, case study, or resource' to the table enum and 'slug or id' to the id/slug properties. However, it does not explain that table is required, whether id/slug are mutually exclusive, or which selector takes precedence.

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 a specific verb ('Fetch') and resource ('full record... for a single blog post, case study, or resource') and clearly states the lookup keys ('by slug or id'). It distinguishes itself from list-oriented siblings by emphasizing 'full record' and 'single' item.

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 conveys a clear use case: retrieve the complete record of one content item when slug/id is known. It does not explicitly mention alternatives like list_content for summaries, but the 'full record' and 'single' language makes the intended context reasonably clear.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.