build_request_to_find_post_by_link_or_aweme_id

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

No annotations are provided, so the description carries full burden for behavioral disclosure. The description offers zero information about what the tool actually does, whether it's a read or write operation, what permissions might be needed, or any behavioral characteristics. The truncated note about endpoints provides no useful 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 incomplete and truncated, showing only a note about endpoints ending with a quote mark. While technically concise, this represents under-specification rather than effective brevity. The content doesn't form a coherent description, making it impossible to evaluate proper structure.

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?

The description is completely inadequate for understanding the tool. With no annotations, no output schema, and a tool name suggesting it finds posts by link or aweme_id, the description fails to explain what the tool does, how it behaves, or what it returns. The truncated note provides no meaningful context for a tool that presumably interacts with some API endpoint.

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% for the single parameter 'X-Fields', which is documented as 'An optional fields mask'. The description adds no additional parameter information beyond what's already in the schema. With high schema coverage and only one parameter, the baseline score of 3 is appropriate since the schema adequately documents the parameter.

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 is completely missing - it only contains a truncated note about endpoints ending with a quote mark, which provides no information about what the tool does. There's no verb, resource, or purpose stated, making it impossible to understand the tool's function. This is worse than a tautology as it's essentially empty content.

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 is provided about when to use this tool. The description doesn't mention any context, prerequisites, or alternatives among the sibling tools. The tool name suggests it finds posts by link or aweme_id, but the description offers no help in determining when this is the appropriate choice versus other post-finding tools in the sibling list.

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