Get ticket form fields

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

Annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=true and destructiveHint=false, so safety and idempotency are covered. The description usefully adds that custom fields and their allowed choices are included, but says nothing about pagination, field-type coverage, or freshness of the schema data.

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 compact sentence with the resource front-loaded and no filler. It is efficient but so short that it leaves obvious questions (scope, workspace behavior) unaddressed.

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?

With rich annotations, a fully documented single parameter, and an output schema, the definition is minimally sufficient. It still omits whether the returned field set is workspace-filtered and whether choices reflect dependent/cascading fields, which an agent calling this before create_ticket would want to know.

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, including the FRESHSERVICE_WORKSPACE_ID default and the '0 means all workspaces' semantics. The description adds nothing about workspace scoping, so baseline 3 applies.

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?

Specific verb ('List') plus resource ('ticket form fields') and it enumerates what is returned (custom fields, API names, allowed choices). It is clearly distinguishable from get_tickets or create_ticket, though it does not name the near-sibling get_agent_fields to differentiate scope.

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?

No explicit when-to-use or when-not-to-use statement, and no mention of alternatives such as get_agent_fields or list_all_requester_fields. Usage is only implied by the fact that API names and allowed choices are needed before building ticket payloads.

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