site_configuration_get

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

With no annotations, the description carries full burden. It states the operation is a read ('returns literal config text') and implies non-destructive behavior via the GET endpoint. While it doesn't elaborate on authorization or rate limits, the behavior is clearly read-only.

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 sentences with zero wasted words. The first sentence delivers the core purpose, the second provides usage guidance and endpoint info. Front-loaded and efficient.

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 no output schema, the description sufficiently explains what is returned: 'literal config text as stored by FastPanel' for nginx, apache, and php.ini. No additional return value details are needed for a simple read 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 coverage is 100% with one required integer parameter 'site_id' described as 'Site id from sites_list'. The description adds the endpoint format '/api/sites/{site_id}/configuration', reinforcing the parameter's role. While the schema already covers meaning, the endpoint info provides extra context.

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 clearly states it reads raw nginx, apache, and php.ini configs for a site. The verb 'read' and specific resource 'configuration' are precise, and it distinguishes itself from sibling 'site_configuration_update' by being the read counterpart.

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?

Explicitly advises using this tool before 'site_configuration_update' to see current state, and provides context about FastPanel's default configs missing hardening. This gives clear when-to-use guidance and mentions the alternative update tool.

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