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

Annotations already declare this a safe, read-only, idempotent, non-destructive, non-open-world operation, so the safety profile is covered. The description adds genuine value by disclosing what data comes back, including rollback-relevant version history, which annotations cannot convey.

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?

A single dense sentence with no padding, front-loaded with the object of the operation and then the payload contents. Every clause adds information an agent can use.

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 read-only getter with full annotation coverage and no output schema, the description does the important work of enumerating return fields, which compensates for the missing output schema. Minor gaps remain around siteId format validity and behavior when the ID does not resolve.

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 coverage is 0% and there is one required parameter, so the description ideally would clarify siteId. It never mentions the parameter directly, but the phrase 'One site's details' combined with the self-evident name 'siteId' (uuid) makes the semantics largely inferable.

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?

Names a specific verb+resource combination ('One site's details') and enumerates the returned content (URL, share link, access settings, versions, people with access), which clearly separates it from neuron_sites_list and neuron_sites_update. It does not, however, explicitly name a sibling the way a 5 would.

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?

Usage is implied rather than stated: you would fetch a single site by ID. The parenthetical 'versions (for rollback)' lightly hints at the neuron_sites_rollback workflow, but there is no explicit when-to-use, when-not-to-use, or alternative routing guidance.

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