Get secure parameters

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

The readOnlyHint annotation already signals a safe read operation. The description adds one useful behavioral detail: $top is not supported server-side, which warns the agent that pagination via $top will fail. It does not disclose other behaviors like default page size, filtering limitations, or whether the values are returned decrypted, but the annotation covers the safety profile.

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 sentence plus a short note, with no wasted words. The core purpose is front-loaded, and the $top caveat is appended efficiently. It earns a 4 for being compact and readable, though it could have used the space to explain parameters instead.

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?

With no output schema, no parameter documentation, and only a one-line description, the tool definition is incomplete for an agent that needs to know how to use skip, filter, select, and orderby. The $top note is a small piece of server behavior, but the overall context is thin for a tool with four undocumented parameters.

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 for the four undocumented parameters (skip, filter, select, orderby). The description only mentions $top, which is not even a parameter in the schema, and provides no meaning for skip, filter, select, or orderby. This is a significant gap for an agent trying to construct a correct request.

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 states a specific verb ('List') and resource ('secure parameters'), and clarifies they are encrypted configuration values. It distinguishes itself from sibling tools like get_string_parameters and get_binary_parameters by naming the resource type, though it doesn't explicitly contrast with those siblings.

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 implies a read-only listing operation, and the readOnlyHint annotation reinforces that. However, it provides no explicit guidance on when to choose this tool over alternatives like get_string_parameters or get_binary_parameters, nor does it mention any exclusions or prerequisites.

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