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

Annotations already set readOnly, idempotent, and non-destructive, so the description is not obligated to restate safety. It adds real behavior beyond that: the return contents, and the rule that inactive agencies are flagged rather than hidden so previously saved picks still resolve. The unexplained reference to a 'Torvex browser extension' adds confusion rather than clarity.

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?

It is a single sentence, front-loaded with the resource and its fields. The parenthetical about the Torvex extension settings is dense and hard to parse, and it competes with the important register_meta_cabinet link.

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 and no parameters, the description carries the burden of saying what comes back, and it does list the key fields. It does not mention return shape or ordering, but for a simple zero-argument list tool it is close to sufficient.

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?

There are zero parameters, so the baseline is 4. The description usefully names the downstream field (`agency_id`) this tool's output feeds, but there are no parameters for it to add meaning to.

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 the specific resource (the workspace's Meta agencies) and enumerates what each entry carries (id, name, commission percent, active flag). It also ties itself to a named sibling, register_meta_cabinet, via its `agency_id` parameter, which separates it from the many nearby list_meta_* tools.

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?

It gives a clear context of use: this is the picker you consult to obtain an `agency_id` for register_meta_cabinet. What's missing is any explicit exclusion or contrast with alternatives such as list_meta_accounts, so an agent must infer that this list is not the same as the account list.

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