tomticket_list_ticket_custom_fields

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

With no annotations, the description usefully adds the behavioral guarantee 'Nao altera dados', making the read-only nature explicit rather than inferred from 'Lista'. It doesn't detail the return structure or permissions, but for a zero-parameter list tool the key non-mutating trait is covered.

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 two short sentences with no filler. The first sentence states purpose and scope; the second states the read-only behavior. Every word earns its place.

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 trivial zero-parameter read-only listing operation, the description provides the essential purpose and safety information. It could add an explicit pointer to sibling custom-field tools or mention what is returned, but nothing is required for a correct invocation.

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?

The input schema has no properties, so there are no parameter semantics to clarify; this is the baseline 4 for a parameterless tool.

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 explicitly states the operation: 'Lista campos personalizados usados em chamados' — a specific verb (list) and a specific resource (custom fields used in tickets). The 'ticket' scope differentiates it from sibling tools like tomticket_list_customer_custom_fields and tomticket_list_organization_custom_fields.

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 intended context is implied by 'usados em chamados', so an agent can tell this is for ticket-related custom fields. However, there is no explicit when-to-use guidance, exclusion, or named alternative among the many custom-field listers in the sibling set.

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