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

Annotations already establish this as a safe, idempotent read. The description adds genuinely non-obvious resolution semantics: agent PATs are scoped to their own workspace, while human sessions fall back to the BUGTAPE_ORG_ID env var. That resolves an ambiguity an agent would otherwise have to discover empirically.

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 sentences with no filler, and the core purpose leads before the resolution caveats. Every clause carries distinct information — the second sentence is pure added value, not restatement.

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 there is no contract for the return shape, so the agent doesn't know which fields (id, name, slug) come back. For a zero-parameter lookup this is a minor gap, and the auth-resolution context is otherwise sufficient to call it correctly.

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, so the baseline is 4. The description correctly avoids inventing parameter guidance and instead spends its words on resolution behavior.

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 ('Return the credential workspace'), so an agent knows it's a lookup of the caller's current org context. It is clearly distinct from every sibling, which all deal with bugs, projects, or stats. The only friction is the name/title/description drift between 'org' and 'workspace', which the reader must reconcile.

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 the tool answers 'which workspace am I operating in?', but never states when to call it or what to do with the result. Usage is inferred rather than stated, and no alternative is named — which is acceptable only because no sibling plausibly competes for this purpose.

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