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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description goes beyond that by disclosing that `today.lastRemain` is authoritative and null until the first push, and that `today.assumedDailyQuota` is a courtesy default rather than a real ceiling — genuinely useful behavioral context about the returned data.

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 purpose is front-loaded in the first clause, and the second clause spends its length on quota semantics that genuinely matter for interpretation. It is dense but every part is justified; the only minor weakness is the fragment-style opening rather than a clear verb.

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, the description carries the burden of explaining returns, and it does so well for the quota fields (including the null-until-first-push behavior). It leaves the shape of the connection object itself implicit, but for a simple read tool this is nearly complete.

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%, and the schema already documents projectId fully, including the 'Get one from list_projects' hint. The description adds no parameter-level meaning beyond that, so the baseline 3 for high-coverage schemas applies.

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 resource (the project's current Baidu Webmaster connection) and its additional payload (today's push-quota usage), which cleanly separates it from siblings like set_baidu_connection, disconnect_baidu, and submit_baidu_urls. An agent can identify this as the read-side counterpart without opening any schema.

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?

Usage is implied rather than stated: it's clearly the tool to call to inspect connection status and remaining quota, but there is no explicit when-to-use, prerequisite, or named alternative guidance. The quota explanation aids interpretation of results but is not routing guidance.

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