getSite

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

There are no annotations, so the description carries the full burden. It clearly indicates a read operation ('Get') with no side effects, but it does not disclose details such as return format, error behavior, or authentication requirements. The description adds minimal behavioral context beyond what the name itself implies.

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 a single concise sentence ('Get details of a specific site') that front-loads the verb and resource. Every word contributes to meaning, with no redundancy or unnecessary detail.

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 is simple with one well-documented parameter and no output schema. The description is sufficient for a basic get operation, though it lacks explicit usage guidance and return value details. Given the low complexity, the description is nearly complete, with only minor gaps.

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 fully documents the single parameter siteId with the description 'ID of the site to retrieve' (100% schema coverage). The tool description does not add any additional meaning about the parameter, so the baseline score of 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?

The description 'Get details of a specific site' uses a clear verb ('Get') and resource ('site'), and the qualifier 'specific' distinguishes it from sibling tools like listSites, which retrieves multiple sites. It unambiguously states the tool's function.

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 implies usage for retrieving a single site's details by ID, but it does not explicitly state when to use this tool versus alternatives like listSites. No exclusions or alternative recommendations are provided, leaving usage context only implicit.

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