pressable_update_site

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

With no annotations, the description carries the full burden of behavioral disclosure. It only states 'update', implying mutation, but fails to explain side effects, required permissions, whether partial updates are supported, or what happens to unspecified fields. This is insufficient for a mutation tool.

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 sentence with no fluff, which is structurally concise. However, it is under-specified rather than appropriately concise, as it omits essential details about the update-able fields and effects.

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 3 parameters, no annotations, and no output schema, the description is highly incomplete. It does not explain what settings can be changed, what the response looks like, or any other contextual details needed for correct invocation, making the description nearly useless for guiding the agent.

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 zero description coverage and the tool description mentions none of the parameters (id, name, php_version). The agent receives no additional meaning beyond the parameter names, and the description fails to compensate for the schema's lack of documentation.

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 uses a clear verb 'Update' and a resource 'settings for a specific site', but 'settings' is vague and doesn't specify which settings (name, php_version) are updatable. It does not distinguish from sibling tool pressable_set_php_version, which overlaps with the php_version parameter.

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?

No guidance is provided about when to use this tool versus alternatives like pressable_set_php_version or pressable_get_site. There is no mention of prerequisites, typical scenarios, or any exclusion criteria, leaving the agent to guess.

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