get_media

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It conveys that this is a read operation ('Lay' = get) and that it uses media_id, but it does not mention return format, error behavior, authentication, rate limits, or any potential side effects.

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 a single short sentence, which is efficient, but it is under-specified. It earns its place by adding the 'by media_id' qualifier, yet it lacks the contextual depth needed for reliable use.

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 an output schema and annotations, the description should explain return values and edge cases. 'Chi tiet' (details) is vague, and there is no information about the response structure, errors, or limits, making the tool description incomplete for robust 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 schema has one parameter (media_id) with 0% description coverage, so the description must compensate. It does mention 'theo media_id' (by media_id), confirming its role as an identifier, but it does not explain acceptable formats, required format, or any special values beyond the schema's basic string type.

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 'Lay chi tiet mot bai theo media_id' (Get details of one post by media_id) states a specific verb (get) and resource (post/media). The phrase 'mot bai' (one post) implies a singular lookup, distinguishing it from list operations, though it does not explicitly mention sibling tools.

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?

There is no guidance on when to use this tool versus alternatives, no exclusions, and no prerequisites. The description simply states the operation, leaving the agent to infer the appropriate context from the tool name and siblings.

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