get_recent_posts

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

With no annotations, the description itself must carry behavioral disclosure. It signals a read-only list operation and a 'most recent' ordering, and it discloses that each post comes with a URN and basic stats. It does not mention pagination, authentication requirements, or exactly which stats are included, so it is adequate but not rich.

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 the primary behavior and followed by a practical use case. Every word earns its place; there is no redundant restatement of the tool name or schema.

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 two-parameter read tool with no output schema, the description adequately covers what is returned (URNs and basic stats) and why an agent would call it. It could be more specific about the shape of the stats, but nothing essential to selecting and invoking the tool is missing.

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%, so the schema already documents 'as' as the profile/company enum and 'count' with default and max. The description adds no parameter-level meaning beyond that, which matches the baseline for fully covered schemas.

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 names a specific verb ('List'), a specific resource ('most recent posts for your profile or company page'), and the key output ('URNs and basic stats'). This clearly separates it from the sibling create/comment/analytics tools without needing to read their schemas.

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 gives a concrete use case: 'Useful for finding post URNs to comment on.' It does not explicitly exclude alternatives or mention get_post_analytics, but the context is clear enough for an agent to choose this over post/comment tools.

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