autotask_get_field_info

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

No annotations are provided, so description must carry the burden. It indicates a read operation (get field definitions), which is correct. However, it doesn't mention potential pagination, rate limiting, or whether it returns all fields or only non-empty ones.

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?

Two concise sentences, front-loaded with the main purpose, followed by usage guidance. No superfluous words.

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?

The tool has simple input (2 params, 1 required) and no output schema, but description explains the return concept (field definitions with picklist values) well. Minor gap: doesn't mention the return format or whether it's a list/object, but sufficient for a simple info lookup.

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 both parameters are documented in the schema. Description adds context about entityType examples and fieldName being optional, but doesn't add depth beyond what schema already provides.

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?

Description clearly states it retrieves field definitions and picklist values for an Autotask entity type. This purpose is distinct from siblings, most of which are create/search/get operations on specific records.

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?

Description explicitly mentions usefulness for discovering valid picklist values, implying when to use (before creating/updating entities). It doesn't contrast with alternatives, but the sibling list has many other get/search tools, so the guidance is adequate.

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