Create Baidu file selection

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

There are no annotations, so the description must carry the full burden of behavioral disclosure. It explains the creation of a selectionId but does not mention side effects, authentication requirements, persistence, or whether the operation is read-only. For a tool that likely mutates state, this is insufficient.

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 a single short sentence with a useful example. It is front-loaded, contains no fluff, and every word earns its place. This makes it easy to parse and quickly understand the core action.

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?

With no output schema, no annotations, and 4 undocumented parameters, the description only covers the core concept. Missing information includes parameter semantics, return format, and usage workflow. Given the tool's moderate complexity, this is not enough for reliable 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?

Schema description coverage is 0%, and the description only explains resultId and select (via the expression example). fsids and paths are entirely undocumented, leaving the agent unable to determine how these parameters are used or when they are needed. The description partially compensates but not enough.

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 function: creates a reusable selectionId from a resultId and an expression. It uses a specific verb ('Create') and resource ('selectionId'), and includes an example expression '1,3,5-9'. This distinguishes it from sibling tools like baidu_read_selection and baidu_analyze_selection.

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 explicit guidance is provided on when to use this tool versus alternatives. The description implies a workflow involving resultId but does not mention prerequisites, exclusions, or sibling tools such as baidu_list_selectable_files. This leaves the agent without clear context for selection.

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