get_v2_story_by_url

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

With no annotations provided, the description carries the full burden for behavioral disclosure. It does not mention any side effects, safety details, authorization needs, or return behavior, offering no transparency about the tool's actions.

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 contains an error ('by id' instead of 'by url') and a helpful callout. While concise, the mistake undermines structure and accuracy.

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 tool's simplicity (1 param, no output schema, no annotations), the description should clearly explain what the tool does and how to use the url parameter. It fails to do so, leaving significant gaps in 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 input schema has a single 'url' parameter with 0% description coverage, and the description completely fails to explain how to use it. The misleading phrase 'by id' adds confusion instead of clarity.

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 states 'Get story object by id' but the tool name indicates 'by url', creating inconsistency. It identifies the resource as a story object but fails to clearly align with the tool's function, reducing 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 description provides a specific warning: 'To work with /s/ links, call /v1/share/by/url first', offering guidance on when not to use this tool. However, it does not mention when to use this tool over siblings like get_v2_story_by_id or get_v1_story_by_url, leaving gaps in context.

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