get_active_profile

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

With no annotations, the description must carry the behavioral burden. It does disclose that connection details are redacted, which is security-relevant, and 'Return' implies a read operation. However, it says nothing about error behavior, whether a profile must already be active, or authentication requirements.

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?

One clear sentence with the action front-loaded and no filler. Every word contributes to the core purpose and the redaction caveat.

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?

For a zero-parameter query the description is mostly sufficient, but there is no output schema and the return shape is only vaguely described as 'profile and redacted connection details'. An agent is left unsure what fields will be present beyond a generic profile object.

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 tool takes zero parameters, and the input schema is already complete. With no parameters to document, the description cannot add parameter-level meaning, so the zero-parameter baseline of 4 is appropriate.

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 names the exact verb ('Return') and a specific resource: the currently active Survey Solutions profile, plus redacted connection details. This clearly distinguishes it from siblings like list_profiles or set_active_profile, which enumerate or change profiles rather than retrieve the active one.

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 gives no when-to-use guidance, prerequisites, or alternatives. It never mentions list_profiles or set_active_profile, so an agent receives no help choosing among profile-related tools beyond the tool name and the word 'active'.

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