ariel_create_post_with_link_card

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

The description discloses the external behavior of fetching Open Graph metadata, which is meaningful beyond the readOnlyHint/destructiveHint annotations. It doesn't cover failure handling when the URL has no OG metadata, but annotations already cover the basic safety profile, so the added behavioral detail is valuable.

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 front-loaded sentence with no redundant filler. It conveys the action, the specific format, and the key behavioral detail in minimal words.

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?

For a simple create action with two required parameters and complete schema descriptions, the definition gives the essential context. It does not describe the return payload or error behavior, and there is no output schema, but invocation-relevant information is sufficient.

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 100%, so the schema already documents text, url, and langs adequately. The description hints that url is used to generate the card, but it does not add significant meaning beyond the schema.

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 uses a specific verb ('Create') and a specific resource ('post with a link card'), and the parenthetical 'fetches Open Graph metadata for preview' adds a distinguishing behavior. This clearly separates it from sibling tools like ariel_create_post and ariel_create_post_with_images.

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 gives clear context: use this tool when creating a post that should include a link card with a preview. It does not explicitly name alternatives or state when not to use it, but the context is specific enough for an agent to infer the appropriate use case.

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