pbs_tfa_list

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

Explicitly marks as READ-ONLY, which is critical since no annotations are provided. Also describes the data returned (per-user entries and lock state).

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 concise sentences that front-load the purpose and output, then provide sibling guidance and prerequisite. No wasted words.

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 simple list operation, the description covers purpose, scope, sibling differentiation, prerequisite, and read-only nature. Output schema handles return values. Complete.

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?

Only one parameter (proximo_target) with 100% schema description coverage. The description adds no additional semantic meaning beyond the schema's detailed explanation, so baseline 3 is appropriate.

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?

Description clearly states the tool lists all users' TFA configuration including per-user entries and lock state. It distinguishes from sibling pbs_tfa_user_get explicitly.

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?

Provides clear advice to use pbs_tfa_user_get for scoping to one user, and mentions prerequisite configuration. This helps the agent decide when to use this tool vs alternatives.

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