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

Annotations already declare readOnlyHint=true, so 'Read only' is largely a restatement, though it reinforces safety. 'Free' adds genuine non-annotation context (no cost/charge), but the openWorldHint=true behavior and any rate limits or auth requirements go undisclosed.

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?

Three short fragments with no filler, and the core purpose is front-loaded. It is efficient, though the terseness edges toward under-specification rather than crispness.

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 should explain what 'who may act' returns — addresses, roles, or permission levels — and it does not. For a lookup tool with an openWorld hint and a closely related sibling (get_representatives), the definition leaves the agent guessing about the result shape and scope.

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%, with the single 'account' parameter documented as a 'Keeta address starting keeta_', so the baseline is 3. The description adds nothing about the account parameter, but the schema already carries the burden.

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 fragment 'Who may act on an account' does convey the resource being fetched, but it never uses a verb like 'retrieve/list' and reads more like a gloss than a definition. It also fails to distinguish itself from siblings such as get_representatives or get_account, which plausibly cover overlapping ground.

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 instead of get_representatives, get_account, or get_directory. The only usage-adjacent hint is 'Free.', which signals cost but not selection criteria.

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