get_profile_posts

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

Annotations already declare readOnlyHint and openWorldHint, so the safety profile is covered. The description adds genuinely new behavioral context beyond them: 'Results are bounded and partial,' warning the agent that output is truncated and not comprehensive — important for a scraping-style read.

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?

Three terse fragments with the resource stated first, then the parameter values, then the result caveat. No filler, though the telegraphic 'feed: posts|replies|media' style is slightly clipped even for a 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?

The output schema exists, so return-format explanation is not required, and the partial-results caveat covers the main behavioral risk. But with 4 parameters at 0% schema coverage, the undefined 'account'/'profile' identifiers and the bound applied by 'limit' leave the agent under-informed for invocation.

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 0% and the schema declares no enums, so the description's 'feed: posts|replies|media' is the only place the feed values are documented — real added value. However, 'account', 'profile', and 'limit' remain entirely unexplained in both schema and description.

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 ('Read one author's posts') and enumerates the three feed variants it can return. It is distinguishable from get_profile in spirit, but never explicitly names what get_profile or search_profile cover, so the boundary is only implied.

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 choose this over get_profile, get_profile_context, get_profile_connections, or search_profile — all siblings that touch the same author. The feed options hint at use cases but neither exclusions nor prerequisites are stated.

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