run_indiehackers_posts

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

With no annotations, the description must carry the behavioral load; it discloses the returned fields and the flat 5-point cost, which is genuinely useful. It omits error behavior (e.g. invalid slug), any rate or auth constraints, and does not confirm the operation is read-only beyond the verb '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?

Two sentences, zero waste: purpose and scope first, then the billing note. The field enumeration earns its place because there is no output schema to document the return shape.

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 single-parameter lookup with no output schema, the description compensates well by listing the returned fields and the cost. It is slightly short on failure modes (what happens with a bad slug) but is otherwise sufficient to invoke correctly.

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 documents that the 'post' parameter accepts a slug or Indie Hackers URL with a concrete example. The description echoes 'slug or URL' but adds no new syntax or format detail, so the baseline 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?

States a specific verb and resource ('Get one Indie Hackers post by its slug or URL') and enumerates the returned fields, which clearly separates it from the plural/list siblings like run_indiehackers_posts_search. It never names an alternative explicitly, so the differentiation is implied rather than spelled out.

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?

'By its slug or URL' implies this is the right tool only when an identifier is already in hand, and that run_indiehackers_posts_search covers discovery. However, no when-to-use condition or alternative is stated outright, leaving the routing to inference.

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