update_questions

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

The description explicitly says 'Replace', which clearly indicates a destructive overwrite of the existing question list. It also notes that the 'questions' parameter is the 'full new list', making the behavioral impact clear. However, it does not mention return values or side effects, but given the lack of annotations, the core behavior is transparent.

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, concise sentence with no redundant or extraneous information. It is well-structured and front-loaded with the action verb.

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 simplicity of the tool and the absence of an output schema, the description provides all necessary context. It clearly identifies the resource (service) and the exact operation (replace questions), making it complete for an agent to invoke correctly.

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?

Both parameters have clear descriptions: 'serviceId' as 'The Topmate service ID' and 'questions' as 'The full new list of intake questions'. The parameter descriptions fully cover their meaning and usage.

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 ('Replace'), the object ('intake questions'), and the scope ('of a specific Topmate service'). It is unambiguous and distinguishes this tool from others like update_service.

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 explicit guidance on when to use this tool versus alternatives (e.g., update_service). The description does not mention conditions or scenarios that would lead an agent to select this tool.

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