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

Annotations already cover the safe-read trait (readOnlyHint=true, destructiveHint=false). The description adds a valuable behavioral constraint not present in annotations: the requirement of a prior login with the same account_link_id. This is meaningful context, though it doesn't disclose pagination behavior or result volume.

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?

Two short sentences with no filler. The critical prerequisite is front-loaded before the action, and every word 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?

The action and prerequisite are stated clearly, but the description omits the surrounding flow: how this step relates to approvals__init, approvals__search, and approvals__page, and what 'result rows' implies about the output. With no output schema and a closely related sibling family, an agent is left without enough context to sequence calls reliably. The presence of the core precondition keeps it from being lower.

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?

The input schema has 100% coverage with descriptions for all six parameters, so the schema carries the semantic burden. The description makes only a passing reference to account_link_id in the context of the login prerequisite, which adds a slight usage link but no new parameter semantics beyond 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 and resource: 'Collect KB Biz Card approvals result rows.' This is clear and distinct from generic tooling. It doesn't explicitly contrast with sibling tools like approvals__search or approvals__page, but the combination of name and action conveys the result-collection role.

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 only usage guidance is the prerequisite that kb_biz_card__session__login must have been called with the same account_link_id. There is no explanation of when to use this tool versus the approvals__init, approvals__search, or approvals__page siblings, nor any alternative or exclusion conditions. An agent must infer the intended call sequence.

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