custom_field_get

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

No annotations are provided, so the description carries the full behavioral burden. It usefully discloses that dropdown/list options are included in the response, but says nothing about behavior for invalid or missing ids, permissions, or error cases.

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?

One front-loaded sentence starting with the trigger condition, with no filler. It could be marginally tighter but wastes nothing.

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-parameter read tool with no output schema, the description covers the essential return shape (type and options). Error behavior and permissions are unstated, but the core invocation need is met.

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 is a single parameter with 100% schema description coverage, so the schema already documents customFieldId as the Trello custom field definition id. The description adds no format, syntax, or id-source detail beyond 'by id', which matches the baseline for fully documented schemas.

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 (get) and resource (one Trello custom field definition) scoped by id, and notes the return content (type plus dropdown/list options). It does not explicitly name the sibling custom_field_options, so differentiation is only implied by the phrase 'one ... by id'.

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?

'Use when you need one ... by id' gives an implied trigger condition but no explicit when-not or named alternative. An agent must infer that custom_field_options is the choice for listing all definitions rather than fetching a single one.

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