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

Annotations already cover the read-only, non-destructive nature of the tool. The description adds useful behavioral context beyond annotations by requiring a prior session login and tying that login to the same account_link_id. It does not detail pagination or return shape, but the safety profile is already disclosed by annotations.

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 two tight sentences with the most important precondition front-loaded. There is no filler, no restatement of the schema, and every phrase earns its place.

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?

For a simple read-only list tool with three optional, self-documenting parameters, the description provides the essential context: what it searches, the required prior login, and the account_link_id binding. No output schema exists, but the operation name and description make the expected list result sufficiently clear.

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 the schema already documents all parameters well. The description's mention of 'same account_link_id' reinforces the schema's guidance but does not add substantial new meaning. page_num and page_size are fully covered by 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 states a specific verb ('Search') and a specific resource ('list of trade partners (buyers/sellers) from tax records'), which clearly differentiates this tool from sibling search/list tools. It is immediately clear what the tool does and what domain it operates in.

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 explicitly states a critical prerequisite: a prior hometax__session__login call with the same account_link_id. This gives the agent a clear when-to-call condition. However, it does not name alternative tools or state when not to use this tool, so it falls short of a 5.

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