Baidu Quota

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

No annotations are provided, so the description carries the full disclosure burden, and it states almost nothing: it does not confirm this is a non-mutating read, does not mention auth/session requirements, and gives no hint about failure modes when the account is unlinked. For a zero-annotation tool this is a substantial gap.

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?

A single short sentence with no filler, and the resource being queried is front-loaded. It is efficient, though its brevity shades into under-specification rather than deliberate terseness.

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?

An output schema exists, so return values need no explanation, and all four optional parameters are fully described in the schema. However, with no annotations and no mention of the Baidu account/session prerequisite, the description is only minimally sufficient 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?

Schema description coverage is 100%, so host, port, scheme and profile are already documented in the schema, and the baseline of 3 applies. The description adds nothing about parameter meaning, though nothing is actually missing from 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 names a specific verb (查看) and resource (百度网盘容量配额), so an agent knows this returns storage quota rather than file listings or connection status. It does not explicitly differentiate itself from the adjacent baidu_status tool, which also reports Baidu account state.

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?

There is no guidance on when to call this versus baidu_status or baidu_info, nor any stated prerequisite (e.g., that a Baidu account must already be logged in and configured). The one-line description leaves usage entirely to inference.

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