permission-getMyPermissions

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

No annotations are provided, so the description must carry the full burden. It only states a simple 'get' operation without disclosing any behavioral traits such as whether it is read-only, what happens if the user lacks permissions, or what format the returned data takes.

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 extremely concise, consisting of a single line and a tag. While efficient, it omits essential context. The structure is minimal but not wasteful.

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 tool's simplicity (1 param, no output schema), a description of one line might be acceptable, but it fails to explain the nature of the returned permissions (e.g., roles, direct permissions) or the significance of 'current user'. Sibling tools with similar names require more differentiation. The description is incomplete for an agent to fully understand the tool's context.

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 input schema has one required parameter (workspacePublicId) with no description and 0% coverage from the schema. The description adds no information about this parameter, its format, or its purpose beyond the property name. Baseline for no coverage and no compensatory info is 1.

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 clearly states the action ('Get') and resource ('the current user's permissions') and specifies the scope ('in a workspace'). It distinguishes from sibling tools like permission-getMemberPermissions which target other users.

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?

No explicit guidance on when to use this tool versus alternatives. The description implies it's for the current user's permissions, but doesn't state prerequisites or conditions. Usage is implied but not clarified.

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