workflow_get_identity

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

Annotations already declare readOnlyHint=true, so the agent knows this is a safe read. The description adds the useful context that GitHub membership isn't required for certain roles, but it doesn't explain what the tool returns, whether identity is always bound, or what happens if no identity exists.

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?

Two short sentences, but the second sentence feels somewhat tangential to the core action and could be considered noise for an agent deciding whether to invoke. The core action is front-loaded, which is good, but the second sentence lacks clear connection to invocation criteria.

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 zero params, readOnly annotation, and no output schema, the description covers the basic purpose. However, it leaves gaps: no indication of what 'bound enterprise identity' means in practice, no error conditions, and no guidance on when a caller should use this vs other workflow_get_* 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?

Zero parameters, so the baseline is 4. The description doesn't need to explain parameter semantics, and it correctly avoids doing so.

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 ('Read') and resource ('the bound enterprise identity'), which is clear and specific. It doesn't explicitly distinguish itself from siblings like workflow_get_related_artifacts or workflow_get_task_context, but the resource is unique enough that an agent can tell it apart.

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 second sentence ('GitHub membership is not required for non-coding Scrum Masters') hints at a use case but doesn't state when to call this tool vs alternatives. There is no conditional guidance, no prerequisites, and no named alternative tool.

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