List Field Options

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

Description adds value beyond annotations by stating returns 'Id and Name' for each option and how to use the result. Annotations already declare readOnlyHint, destructiveHint, idempotentHint, openWorldHint, and the description is consistent.

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 sentences, no wasted words. Front-loaded with purpose, then usage guidance. Highly concise and structured.

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 simple list tool with annotations and no output schema, the description covers what it returns (Id, Name) and how to use the result. Completeness is good, though it could mention pagination more explicitly.

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 coverage is 100% with descriptions for all three parameters. Description mentions filter but doesn't add significant new meaning beyond the schema's examples. Baseline score of 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 'List individual options within a dropdown-type custom field' with specific verb and resource. Differentiates from siblings like ploomes_fields_list and ploomes_fields_options_tables_list by focusing on listing options within a specific table.

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?

Explicitly instructs to filter by 'OptionsTableId' and gives a practical usage hint: 'Use the Name as ObjectValueName when writing OtherProperties.' No explicit when-not-to-use, but alternatives are available among siblings.

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