get_v1_location_medias_recent

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

With no annotations, the description must cover behavior but only states 'Get location recent medias'. It does not disclose pagination, authentication needs, error handling, or any constraints, providing minimal transparency.

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 brief, but the first line repeats the endpoint path already in the tool name, adding redundancy. The second line is a simplified rephrase. It is concise but could be more efficient by removing the endpoint line.

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 simple tool with 2 parameters and no output schema, the description is incomplete. It fails to clarify return format, parameter details, or selection criteria, insufficient for correct agent 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?

The input schema has two parameters with no descriptions (0% coverage), and the tool description adds no meaning beyond the schema. For instance, the 'amount' parameter's unit or behavior is not explained, leaving the agent guessing.

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 recent medias', clearly indicating the verb 'get' and resource 'location recent medias'. However, it does not distinguish from sibling tools like 'get_v1_location_medias_top' or the chunk variants, missing an opportunity to differentiate.

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 vs alternatives such as 'get_v1_location_medias_top' or the chunk endpoints. The description lacks context for selection, leaving the agent uninformed.

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