autotask_get_company_site_configuration

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

With no annotations provided, the description fully conveys that this is a read-only operation (Get). It explains the nature of site configurations (tenant-defined fields) and implies that the tool returns field information. No annotations to contradict, so no contradiction flag.

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?

Three sentences are concise and front-loaded: first sentence states the action, second explains what site configurations are, third provides usage guidance. No unnecessary 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?

Given the tool has one simple parameter and no output schema, the description is complete enough for an agent to understand the tool's purpose, when to use it, and what it returns (field discovery). It lacks details about the output structure, but that may be acceptable without an output schema.

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 one required parameter with 100% description coverage (companyId described as 'The company ID whose site configuration records should be returned'). The description adds context that this is for a company and ties to discovering fields for subsequent updates, but the schema itself is clear.

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 it retrieves site configuration records for a company in Autotask, clarifying that these contain tenant-defined fields for per-company configuration data. It also distinguishes its purpose from the sibling tool autotask_update_company_site_configuration by suggesting this tool be called first.

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 description clearly states when to use this tool: 'Call this first to discover which fields are available before calling autotask_update_company_site_configuration.' This provides explicit guidance on ordering and alternatives, helping the agent decide to use this tool before the update tool.

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