Get My Coordination Role

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

Annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=false, and destructiveHint=false, so the safety profile is fully covered elsewhere. The description contributes the shape of the result (role, tasks, instructions), which matters because there is no output schema, but it says nothing about failure modes (e.g., what happens if no role is assigned) or scope of the returned tasks.

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 front-loaded sentence with no filler; the core action and the returned contents are stated immediately and nothing is padded or repeated.

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-argument, read-only lookup the description is adequate: it names the action and the three things returned. However, with no output schema to fall back on, it leaves the agent guessing about result structure and about the no-role-assigned case, which a slightly longer description could have covered.

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, which sets the baseline at 4. There is nothing for the description to clarify or compensate for, and no misleading parameter language is present.

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 specific verb and resource ('Get your current role') and enumerates the payload ('assigned tasks, and role-specific instructions'). It is unambiguous on its own, but it does nothing to distinguish it from siblings such as list_tasks, get_task_detail, or list_agents, which superficially overlap with the 'assigned tasks' portion.

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?

There is no explicit when-to-use, no prerequisite, and no named alternative. The only signal is the possessive 'your', which weakly implies this is a self-introspection call (e.g., at session start) rather than a query about other agents — that is inference, not guidance.

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