set_survey_properties

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

The description indicates a write operation ('Set'), which aligns with readOnlyHint=false. Annotations already convey that it is non-destructive and open-world. The description adds no further behavioral details (e.g., side effects, rate limits, authentication needs) beyond what annotations provide.

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 concise (one sentence) but lacks critical context, such as the restriction on setting 'sid' and 'active'. It is not front-loaded with the most important information, and the brevity sacrifices completeness.

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 two parameters (one an object) and no output schema, the description should explain key behaviors like the immutability of 'sid' and 'active', but it does not. The description is insufficient for an agent to fully understand the tool's operation and constraints.

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 100% coverage with descriptions for both parameters (iSurveyID and aSurveyData). The description adds no additional meaning beyond the schema, so it meets the baseline of 3.

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 verb ('Set') and resource ('survey properties'), making the tool's purpose understandable. However, it does not distinguish it from sibling tools like set_group_properties or set_question_properties, and it omits the important constraint that 'sid' and 'active' cannot be set (though that is in the schema).

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 on when to use this tool versus alternatives (e.g., get_survey_properties for reading, activate_survey for activation). There is no mention of prerequisites or context-specific scenarios.

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