Get quota properties

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and idempotentHint=true. The description adds value by specifying the underlying API method and authentication details, confirming the read-only nature and providing operational context beyond annotations.

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 with two substantive sentences plus a line for method and authentication. It is front-loaded with the purpose and contains no extraneous information.

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), rich annotations, and thorough input schema, the description provides enough context. It covers authentication and the underlying method, making it complete for a read-only tool.

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?

Input schema coverage is 100% with descriptive parameter names and descriptions. The description's mention of 'selected quota properties' is generic but does not add new meaning beyond the schema. Baseline score of 3 is appropriate as the schema already sufficiently documents parameters.

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 explicitly states 'Read selected quota properties,' which clearly identifies the action (read) and resource (quota properties). This distinguishes it from sibling tools like limesurvey_set_quota_properties (write) and limesurvey_delete_quota (delete).

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 provides context on when to use it (reading quota properties) and the underlying RemoteControl method. It also includes authentication guidance ('do not provide a session key'). However, it does not explicitly state when not to use it or compare with alternatives, though siblings imply the differentiation.

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