autotask_get_field_info

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

Accurately describes behavior as retrieving field definitions, but lacks disclosure of potential side effects, permissions, or response structure. No annotations to contradict.

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, front-loaded sentences with no redundant information.

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?

Provides the essential purpose but omits details about the return format, which would be helpful given no output schema. Overall adequate for a metadata query tool.

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 description covers 100% of parameters, so description adds minimal additional meaning. The phrase 'discovering valid values for any picklist field' weakly hints at using fieldName.

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?

Clearly states it retrieves field definitions including picklist values for an Autotask entity type. The description distinguishes from sibling CRUD tools by focusing on metadata discovery.

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?

Indicates usefulness for discovering picklist values but does not specify when not to use or mention alternatives among the many sibling tools.

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