bricks_wp_get_post

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

With no annotations, the description carries the burden of behavioral disclosure. It reveals what data will be included in the response (full content, excerpt, categories, tags, featured image, meta) and confirms CPT support. The 'Get' verb implies a read-only operation; while it doesn't mention error handling, this is adequate for a simple retrieval tool.

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 short sentences with no filler. The tool's purpose and notable scope are front-loaded, and every sentence is purposeful.

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 this is a single get with no output schema, the description enumerates the main returned fields and the only special usage consideration (CPT). It does not address error behavior or authentication, but for a straightforward read operation this is reasonably complete.

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%, with both post_id and post_type clearly described. The description reiterates the post_type usage ('Works on custom post types via post_type'), but the schema already provides thorough parameter guidance, so the description adds limited additional value on top of 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?

The description states a specific action ('Get') and resource ('a single WordPress post'), and enumerates what it returns: full content, excerpt, categories, tags, featured image, and meta. This clearly distinguishes it from list, create, and update sibling tools.

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 clearly indicates this is the tool to use for a single post with enriched details, and it highlights the custom post type capability. It doesn't explicitly name alternatives like bricks_wp_list_posts, but the context unambiguously defines its purpose.

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