Get this account's statuses and custom fields

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

Annotations already declare readOnlyHint, openWorldHint, and destructiveHint, so the description adds valuable semantic context beyond those flags: it explains that statuses are account-defined and that default codes like 2=Open may be unused. This helps the agent understand the data's reliability without contradicting the annotations.

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 efficient: the first sentence captures the full scope, and the second adds an essential warning. No filler or repetition; every sentence earns its place. The structure front-loads the purpose and then provides practical context.

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 zero-parameter metadata tool with no output schema, the description is highly complete. It enumerates all data categories returned (codes, labels, choices) and explains why the tool is important for filtering and writing. The sibling tools are all operational, so this description fully covers the tool's role.

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 are no parameters, so the baseline is 4 per the rubric. The description does not mention parameters (there are none), and the empty schema fully covers this aspect, so no additional parameter information is needed.

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 clearly states the tool returns the full field inventory for the account, listing statuses, priorities, sources, ticket types, and custom fields. It uses specific verbs and resource scope ('real field inventory') and is distinct from sibling tools that operate on tickets or articles.

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 advises to read this tool 'before filtering or writing', which is a concrete usage recommendation. It also warns against relying on Freshdesk defaults because accounts define their own statuses, effectively specifying when this tool is necessary and preventing misuse.

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