survey_agent_settings_save

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

With no annotations provided, the description must disclose behavioral traits. It indicates mutation via 'Save' but fails to specify whether this overwrites, upserts, or creates, nor does it mention error conditions or side effects. Critical context for a mutation tool is missing.

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 very short—two sentences—and front-loads the core purpose. It contains no filler, but the extreme brevity limits its value for complex tools.

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 presence of an output schema (unseen) and two required parameters, the description lacks completeness. It doesn't explain the effect on existing settings, the behavior when survey_id is invalid, or how errors are reported. A more thorough description would significantly improve agent decision-making.

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%, so the description must compensate. It adds meaning to settings_json by clarifying it can be an object or nested under 'settings', which helps the agent format the input correctly. However, survey_id remains undocumented beyond the schema field name.

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 the action 'Save survey settings' and provides a format hint for settings_json. It distinguishes itself from sibling survey_agent_settings_get by being the write counterpart, though it doesn't explicitly note the relationship.

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 on when to use this tool vs alternatives like survey_agent_settings_get or other survey tools. There is no mention of prerequisites, idempotency, or conditions under which saving is appropriate.

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