get_profiles_posts

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

Discloses credit cost (1 credit per call), which is helpful. However, no annotations exist, and description lacks detail on rate limits, side effects, or pagination nuances. Minor inconsistency: 'last 50' implies a fixed set, but schema supports pagination for more results.

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?

Extremely brief (two sentences), but lacks structure. The single functional sentence could be more informative, and the credit mention is useful but not fully earned.

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 4 parameters, no output schema, and no annotations, the description is insufficient. It does not explain response format, pagination behavior (start, paginationToken), or how 'postedAt' filter works, leaving gaps for an agent.

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 covers 100% of parameters with descriptions. The description adds no additional meaning beyond 'Get last 50 posts', so baseline score of 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?

Description explicitly states 'Get last 50 posts of a profile', providing a specific verb and resource. It clearly distinguishes from sibling tools like 'get_post' (single post) and 'get_article' (articles).

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?

No guidance on when to use this tool versus alternatives (e.g., 'get_profile_data', 'get_profiles_comments'). Missing context on preferred use cases or exclusions.

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