mediabyshortcode

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

No annotations are provided. The description only says 'getting', which suggests a read operation, but does not disclose any behavioral traits such as what happens if the shortcode is invalid, rate limits, or return format. The minimal description fails to provide sufficient 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 extremely short, consisting of only four words. While concise, it lacks structure and important details. It could be considered under-specified rather than efficiently concise.

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?

The tool has no input parameters and no output schema. The description does not explain how the shortcode is provided (e.g., via a separate context or path), nor does it describe the return value. This makes it incomplete and difficult to use.

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 description mentions retrieving by shortcode, but the input schema has no parameters. This creates a contradiction: the tool requires a shortcode but has no field for it. The schema coverage is 100% with zero parameters, so the description's implication of a parameter is misleading.

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 clearly states the tool retrieves a post or reel by shortcode. It distinguishes itself from sibling tools like 'posts' and 'reels' which likely don't use shortcode, but the description does not explicitly highlight this uniqueness.

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?

The description implies use when a shortcode is known but provides no guidance on when to use this tool versus alternatives like 'posts', 'reels', or 'get'. There is no mention of prerequisites or when not to use it.

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