share_url_parse_tool_wrapper

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

No annotations are provided, so the description must convey behavioral traits. It states that the tool parses a URL and returns code, msg, and data, implying a read-only operation, but does not disclose side effects, authentication needs, or any potential errors. The description lacks sufficient behavioral context.

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 brief and structured with a purpose statement, parameter list, and return fields. It is appropriately sized for a simple tool, though it could be more front-loaded with the purpose.

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 tool with one parameter and an output schema, the description covers the core purpose and return structure (code, msg, data). However, it lacks usage guidance, behavioral detail, and any differentiation from siblings, leaving the agent with an incomplete picture for correct invocation.

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 schema has 0% description coverage (only type string), but the description adds meaning by labeling 'url' as a 'video share link'. However, it does not provide format, constraints, or examples, so it adds minimal value 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 clearly states the tool's purpose: 'parse video share link, get video info'. It specifies both the verb (parse) and the resource (video share link), and the sibling tools (share_text_parse, video_id_parse) are distinct, indicating this tool is specifically for URL parsing.

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?

No guidance on when to use this tool versus its siblings (share_text_parse_tool_wrapper, video_id_parse_tool_wrapper). There is no mention of prerequisites, contexts, or exclusions, leaving the agent without direction for tool selection.

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