Analyze selected Baidu files

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

With no annotations, the description carries the full burden of disclosing behavior. It describes the output content but fails to state whether the operation is read-only, whether selectionId must come from a prior selection step, how chunkSize affects processing, or any side effects and permission requirements. Operational behavior remains 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 a single sentence that front-loads the verb 'Summarize' and packs the output aspects into a compact list. There is no wasted wording or redundant repetition of the tool name.

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 and no annotations, the description should explain the tool's integration with other selection tools, the origin of selectionId, and the meaning of chunkSize. It states the purpose but omits these critical contextual details, leaving an agent uncertain about how to safely invoke the tool in a workflow.

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%, so the description must compensate, but it does not explain either parameter. 'Selected files' loosely implies selectionId identifies a prior selection, but chunkSize's meaning, constraints, and effect are entirely absent. No parameter-level detail is provided.

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 uses the specific verb 'Summarize' and clearly identifies the resource as 'selected files', enumerating the output dimensions (key points, actions, tags, value judgment, suggested classification). This makes the tool's function clear, though it does not explicitly distinguish itself from sibling tools like baidu_read_selection or baidu_plan_organize_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?

The description implies usage—when the user needs a summary of selected files—but provides no explicit guidance on when to prefer this tool over alternatives, nor any exclusions or prerequisites. It does not mention that a prior selection must exist or reference related selection tools.

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