Get question properties

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false. The description adds value by specifying the underlying method (`get_question_properties`) and clarifying authentication behavior (no session key needed). No contradictions.

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 two sentences: the first states the purpose, and the second provides implementation and authentication context. No unnecessary words, front-loaded, and every sentence adds value.

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 (not shown but indicated), the description need not explain return values. It covers purpose, method, and a key authentication detail. With 4 parameters (1 required), it provides sufficient context for an agent to use the tool correctly, though it could mention that the tool supports both JSON and Markdown output formats.

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 coverage is 100%, so the baseline is 3. The description does not add any additional meaning beyond what the schema provides for each parameter. It says 'Read selected question properties' but does not elaborate on the available parameters like `language`, `properties`, or `response_format`.

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 starts with 'Read selected question properties,' clearly stating the verb (Read), resource (question properties), and scope (selected). This distinguishes it from sibling tools like `limesurvey_set_question_properties` (write) and other getters for surveys, groups, etc.

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?

The description includes a guideline to not provide a session key because authentication is handled by the service account. While it does not explicitly state when to use this tool over alternatives, the naming and sibling context make it obvious. A slight improvement could be adding a mention that this is for reading, not writing, questions.

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