get_v1_location_medias_recent_chunk

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

Annotations already declare readOnlyHint, openWorldHint and destructiveHint=false, so the safety profile is covered. The description adds genuinely useful operational context beyond that: one page per call, pagination via max_id, and that this is a live billed request to Instagram. It stops short of describing rate limits or failure modes, so a 4 rather than 5.

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 compact sentences, each earning its place: purpose, pagination mechanics, alternative sibling, then cost/nature of the call. The primary action and the required parameter are front-loaded.

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?

No output schema exists, and the description partly fills that gap by framing the response as one page per call with a max_id cursor. Cost and live-request nature are disclosed. What a page actually contains (fields per post) is left implicit, which is a minor residual gap.

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%, so the description must compensate, and it does: it tells the agent to pass location_pk and that max_id comes from the previous response for pagination. That gives meaning to both parameters beyond their bare names and types, though it doesn't state location_pk's expected format or source.

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+resource ('List recent posts made at an Instagram location') and immediately distinguishes itself from the sibling by naming get_v1_location_medias_top_chunk for top posts. An agent can pick between the two without opening either schema.

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?

Explicitly says to pass location_pk, to paginate with max_id from the previous response, and to use the top-posts sibling instead when appropriate. Both the when-to-use and the alternative are stated outright.

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