get_v1_location_medias_recent_chunk

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

No annotations exist, so the description must fully convey behavioral traits. It only states it gets a chunk of recent medias, without mentioning authentication, rate limits, pagination details, or what a chunk entails. The behavioral disclosure is very limited.

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 extremely short (two lines) but is under-specified rather than concise. It wastes space by repeating the title and HTTP method without adding useful information. The brevity misses opportunities to convey necessary details.

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 tool has 2 parameters, no output schema, and no annotations, the description is grossly incomplete. It does not explain the chunk concept, pagination via max_id, or expected response structure. The description is insufficient for an agent to use the tool correctly.

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?

The input schema has 2 parameters (location_pk, max_id) with 0% description coverage. The description does not explain any parameters, so it adds no meaning beyond the schema. It fails to compensate for the lack of parameter descriptions.

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 recent medias' which indicates the verb 'get' and resource 'location medias recent chunk'. However, it is vague about what 'chunk' means compared to similar siblings like get_v1_location_medias_recent. The purpose is discernible but lacks specificity to distinguish from alternatives.

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 usage guidelines are provided. The description does not mention when to use this tool versus others like get_v1_location_medias_recent or get_v1_location_medias_top. There is no guidance on context or alternatives.

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