get_v1_location_medias_top_chunk

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

With no annotations, the description fully carries the burden of behavioral disclosure. It only states it's a GET for top medias chunk but does not explain pagination (e.g., use of max_id), rate limits, authentication needs, or what 'chunk' entails in terms of size or ordering.

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?

The description is very short (one sentence plus a redundant HTTP method line). It is concise but at the expense of necessary detail. The bracketed '[GET /v1/location/medias/top/chunk]' adds no value as it repeats the tool's name.

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?

Given the absence of output schema, annotations, and parameter explanations, the description is woefully incomplete. It fails to clarify pagination, response format, or how this tool differs from siblings. For a 2-parameter tool with no structured context, this is insufficient.

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%. The description does not mention or explain the two parameters (location_pk and max_id). Despite the schema having titles like 'Location Pk' and 'Max Id', the description adds no value to clarify their meaning or usage.

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 states 'Get location chunk of top medias', which provides a clear verb and resource. However, it does not differentiate from sibling tools like 'get_v1_location_medias_top' (which may return all top medias) or 'get_v1_location_medias_recent_chunk' (which returns recent chunks). The word 'chunk' hints at pagination, but this is not explicit.

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 is provided on when to use this tool versus alternatives. There is no mention of use cases, prerequisites, or when not to use. The description lacks context for selection.

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