get_profile_permissions

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

With no annotations, the description carries the behavioral burden. It discloses that the tool returns effective flags and that the profile defaults to active unless a specific profile is requested. However, it does not explain what flags are returned, whether this is read-only, or how "effective" is computed relative to permission modes.

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?

A single 12-word sentence that front-loads the core purpose and includes the key behavioral distinction. Every word contributes; there is no filler or redundancy.

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?

The tool is simple with one optional parameter and no output schema, so the description covers the main calling context. Still, it leaves gaps: the return shape of the "permission flags" is unspecified, and there is no mention of how this relates to permission modes or sibling permission-analysis tools.

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 schema documents the optional "profile" parameter, and the description adds semantic value by clarifying that the active profile is used when omitted and a requested profile can be supplied. This default-vs-explicit behavior goes beyond the schema's minimal "Optional configured Survey Solutions profile name."

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?

States a clear verb and resource: "Show effective permission flags" for the active or requested profile. The phrase "effective permission flags" distinguishes it from generic profile tools, though it does not explicitly differentiate from siblings like describe_permission_modes or get_active_profile.

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 usage by saying "active or requested profile," but it provides no explicit guidance on when to use this tool versus siblings such as describe_permission_modes, recommend_permission_mode, or get_active_profile. No exclusions or alternatives are mentioned.

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