get_account_custom_attribute

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

With no annotations, the description carries full burden. It states 'List' implying a read operation, but does not mention pagination, limits, or that it actually lists only one model type per call due to the required attribute_model parameter. The phrase 'all custom attributes' is slightly misleading.

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?

The description is a single sentence with no unnecessary words. It is front-loaded with the verb and resource, making it efficient.

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 one required parameter, the description should mention that the parameter filters by attribute model. Without that, the agent may assume it lists all custom attributes unconditionally. No output schema exists, but the return format is not described either.

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%, so the input schema already documents the attribute_model parameter with enum and description. The description adds no extra meaning beyond 'custom attributes', and does not mention that the parameter is required or how it filters results. 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?

The description 'List all custom attributes in an account' clearly states the action (list), resource (custom attributes), and scope (in an account). It effectively distinguishes from sibling tools like add_new_custom_attribute_to_account or get_details_of_a_single_custom_attribute.

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?

The description provides no guidance on when to use this tool versus alternatives such as get_details_of_a_single_custom_attribute or when filtering by attribute_model is needed. No context or exclusions are given.

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