get_v1_share_by_url

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

Without annotations, the description shows an example output and URL format constraints, but it does not address authentication, error cases, or read-only behavior. The example is helpful but incomplete.

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 short but suffers from truncation and informal language. It conveys the key points but is not well-structured, reducing readability.

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, the description provides an example output and clarifies the scope. It lacks explanation of error handling, data interpretation, and edge cases, making it adequate but not comprehensive.

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 provides an example URL and mentions that the link must contain '/s/', adding value beyond the schema's basic string type. However, it does not formally describe the parameter format or constraints.

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 explicitly states it works for stories and highlights only and provides an example output, distinguishing it from siblings like get_v1_media_by_url. However, the formatting is messy with truncation, and the purpose could be stated more cleanly.

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 indicates the tool is for stories/highlights and suggests alternative endpoints, but it does not fully explain when to use this over other similar share tools or provide comprehensive exclusion criteria.

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