get_post

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

Discloses conditional return behavior (single vs multiple posts) and fields (items, financial_data, summaries). No annotations, so description carries full burden; missing auth needs, rate limits, or error cases.

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, front-loaded with purpose. No redundant information.

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?

With output schema present, description covers return format variations. Missing error handling or prerequisites, but sufficient for a simple retrieval tool.

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?

Explains 'slug_or_date' parameter with examples ('shijie-kucha-2024-01-15' or ISO date). Schema has no description, so this adds significant meaning beyond type string.

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?

Clear verb+resource: 'Get a full post' by identifier. Distinguishes from sibling tools (discover, list_recent, search_news) which are for discovery, not retrieval by identifier.

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?

Specifies when to use: when you have a slug or ISO date. Implicitly suggests using siblings otherwise, but does not explicitly list alternatives.

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