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

With no annotations provided, the description carries the full behavioral burden. It states the core behavior—returning the full markdown of a published post—but does not disclose error behavior, access restrictions, or explicitly confirm a read-only side-effect profile beyond the implied 'get'.

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 short, front-loaded sentence with no filler. Every word contributes to understanding the resource, the scope, and the lookup mechanism.

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?

This is a low-complexity single-parameter getter with no output schema and no annotations. The description adequately states what is returned and how to identify the target post, making it sufficient for normal use; minor gaps remain around error handling and access behavior.

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 100%, and the schema already explains 'slug' as 'The slug from list_writing'. The description's phrase 'by slug' adds no new semantic detail beyond what the schema provides, so 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 clearly identifies the resource as a single published post and the lookup key as the slug. This distinguishes it from sibling tools like get_case_study, get_contact, and get_resume, 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?

Usage context is implied rather than explicit: the schema notes that slug comes from list_writing, suggesting an agent should list posts first. However, the description does not explicitly state when this tool should be preferred over search_writing or other getters, nor does it mention exclusions.

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