get_v1_story_by_url

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

No annotations are provided, and the description fails to disclose essential behavioral traits such as idempotency, authentication requirements, or error handling. The minimal description offers no insight into side effects or constraints beyond the vague 'Get story object'. The tool's behavior is largely opaque.

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 very short, with only one functional sentence and an attention note. It is front-loaded with the HTTP path and key caveat. No redundancy; every part adds information. However, the note's placement before the main purpose could be confusing.

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 input schema (one param) and no output schema, the description should clearly define input constraints, output shape, and when to use alternatives. It fails to do so, leaving gaps about error scenarios and response structure. The 'by id' misstatement undermines completeness.

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 sole parameter 'url' is of type string, but the description adds no semantic value—it incorrectly refers to 'by id' instead of 'by url'. With 0% schema description coverage, the description should clarify URL format (e.g., full vs. short link, required prefix) but does not.

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 claims 'Get story object by id' but the tool name and parameter expect a URL, contradicting the resource identifier. Sibling tool get_v1_story_by_id exists, but no differentiation is provided. The attention note about /s/ links adds confusion rather than clarity.

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 attention note explicitly advises using get_v1_share_by_url first for /s/ links, offering some guidance on when to avoid this tool. However, it does not specify when to use this tool over other story-related siblings (e.g., get_v1_story_by_id, get_v1_story_download). The guidance is incomplete.

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