List Tracker local fields

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

Annotations already declare readOnlyHint, idempotentHint, and openWorldHint, so the safety profile is covered. The description adds that the result is a flat list and that each item carries a key and field_schema, which is useful shape context but not a rich behavioral disclosure (no pagination or rate-limit info).

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 sentences, front-loaded with the scope constraint, and every clause carries information (scope, return shape, sibling contrast, param origin). No filler.

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 single-param read-only list with annotations covering safety, this is nearly complete: it explains what local fields are, how they differ from globals, what the output items contain, and where queue_id comes from. Minor gap is that there is no output schema and the description only lightly describes the returned structure.

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% and the queue_id parameter is fully documented in the schema (queue key or numeric id, case-sensitive). The description reinforces the source of queue_id by naming queues_list, which adds marginal routing value.

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?

States a specific verb+resource ('local fields' scoped to a queue) and explicitly distinguishes from the global sibling tracker_fields_list. The contrast 'Local fields differ from global fields' makes the distinction unmistakable.

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?

Explains the scope (one queue) and points to localfields_get as the consumer of the returned key, plus names fields_list as the global alternative. No explicit when-not-to-use guidance, but the context is clear enough to select this tool.

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