get_post

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

No annotations present, so description must cover behavioral traits. It does not mention permissions, side effects, rate limits, or whether the action is idempotent/read-only (though inferred). The citation instruction is a usage rule, not tool 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?

Two sentences: first covers purpose and content, second adds citation requirement. No unnecessary words, but the citation instruction could be considered separate from tool description.

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 retrieval tool with one parameter, the description adequately specifies the output content. However, it lacks details on error conditions, slug format validity, or response structure (though no output schema exists).

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?

Input schema has 100% description coverage for the single 'slug' parameter, which already explains its purpose. The description does not add further parameter details; the content list (HTML, CSS, etc.) relates to output, not parameter semantics.

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?

Clearly states 'Get full details of a Looba snippet post' with explicit content (HTML, CSS, JS, author, license). The verb 'get' and resource 'post' are precise, and it distinguishes from siblings like list_posts (listing vs. detail) and search_by_author (search vs. slug-based retrieval).

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?

Provides an implicit usage context: retrieving details of a specific post by slug. The citation instruction is a post-usage policy but does not explicitly guide when to use this tool versus alternatives. No comparison with sibling tools or conditions for not using it.

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