location.default

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

No annotations are provided, so the description carries the full burden. It merely says 'get' without disclosing whether this is a read-only operation, whether authentication is required, what the coordinates do, or what happens when no default address exists. This is a significant gap for a tool with two unexplained parameters.

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 is easy to parse and contains no fluff. It earns points for conciseness, but brevity here comes at the cost of omitting essential parameter context.

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?

Given the tool has two parameters with defaults, an output schema, and no annotations, the description is too thin to support correct invocation. The agent cannot infer the relationship between the coordinates and the default publish address, making the tool underspecified for real use.

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 never mentions latitude or longitude. The agent has no way to know whether these coordinates are inputs to a lookup, outputs of the address, or geolocation hints, and their defaults (Shanghai coordinates) add further confusion.

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 states a specific verb and resource: '获取账号默认发布地址' (get account default publish address). However, the presence of latitude/longitude input parameters is not reflected in the description, so it is unclear whether the tool returns the account's default address or computes a default based on coordinates, creating ambiguity.

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 use this tool versus alternatives, no prerequisites, and no excluded cases. The only implied usage is a restatement of the purpose, which is not enough to route an agent correctly.

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