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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds useful behavioral context beyond annotations: the required settings:read scope and the fact that changing the value is outside this tool's role and must be done by a person in the admin.

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 short, front-loaded with the read-only constraint, and every clause contributes: safety, scope, returned setting values, and the admin-only change boundary. There is no filler.

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 simple one-parameter read tool with full schema coverage and annotations, the description gives the key missing context: what setting is returned, its possible values, the required scope, and that mutations are handled in admin. It is essentially complete, with only minor room for a more explicit return description.

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 100%, and the sole `site` parameter is already documented as the Site ID from list_sites. The description adds no additional parameter semantics, which is acceptable given full schema coverage but does not exceed the baseline.

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 identifies the resource as the embedded form's bot check and states the relevant values: form_turnstile required / off. It is clear what setting is being read, though it does not use an explicit verb such as 'returns' and only indirectly distinguishes itself from broader settings tools.

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?

It clearly frames this as a read-only lookup and explicitly says changing the setting is a person's job in the admin, which tells the agent not to use this tool for mutation. It does not name a specific alternative sibling such as get_settings, but the when-not guidance is clear.

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