get_workspace_context

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

Lists the specific information returned (mode, org count, project count, active scope, role). No annotations provided, so description carries full burden; it adequately discloses the read-only nature and content but does not mention any potential side effects or permissions.

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 concise sentences: first lists outputs, second gives usage guidance. No superfluous information.

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?

Perfect completeness for a 0-parameter read tool with no output schema. Lists all returned fields and provides usage context, sufficing for agent orientation.

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?

No parameters exist; baseline score of 4 applies. Description adds value by explaining what the tool returns, which is relevant for an info tool.

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?

Clearly states it shows the current Flow Relay context including mode, organizations, projects, active scope, and caller role. 'Show' verb paired with 'workspace context' resource. Easily distinguished from siblings like list_projects or set_active_project.

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?

Explicitly says 'Good first call to orient yourself before other tools,' providing clear guidance on when to use it as an initial exploration step.

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