get_my_role

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

No annotations are provided, so the description carries the full disclosure burden. It lists the output contents (role, tasks, instructions) but does not explicitly state that the operation is read-only, requires no special permissions, or has no side effects. The verb 'Get' implies safety, but this is left implicit rather than disclosed.

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 of nine words, front-loading the verb and direct object. It is perfectly concise with no redundant or filler content.

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, the description enumerates the three return components: current role, assigned tasks, and role-specific instructions. This is adequate for a parameterless self-inquiry tool, though it does not describe the structure or format of the returned data.

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 accepts zero parameters, so the empty schema fully describes the input. The description adds no parameter semantics, but none are needed; per guidelines, a zero-parameter tool receives a baseline score of 4.

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 uses the specific verb 'Get' and clearly identifies the resource: the agent's current role, assigned tasks, and role-specific instructions. This distinguishes it from sibling tools like list_tasks or get_task_detail, which focus on individual tasks rather than the agent's overall role context.

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 is provided on when to use this tool versus alternatives such as list_tasks or get_task_detail. The pronoun 'your' implies self-context, but the description does not state when this tool should be preferred or any exclusions.

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