Server info

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety and determinism profile is fully covered by structured data. The description adds the scope of returned metadata (that auth and policy details are included), which is useful but is content rather than behavior; it says nothing about freshness, caching, or auth requirements.

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 preamble and no filler. The verb and the payload categories are stated immediately, which is the ideal shape for a zero-argument informational tool.

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?

An output schema exists, so the description is not obligated to describe return values, and the enumerated categories give a useful preview of the payload. Zero parameters means no argument documentation is required. The only real omission is guidance on when this tool should be preferred over 'workspace_guide'.

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 per the rubric the baseline is 4. There are no arguments whose semantics need explaining, and the schema confirms an empty, additionalProperties=false object.

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 names a specific verb ('Return') and enumerates the resource domains covered: server, workspace, project-context, auth, policy, and fixed-tool metadata. This is concrete enough that an agent knows exactly what class of information it retrieves. No sibling tool covers the same ground, so explicit differentiation isn't needed.

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 indication of when to call this tool, in what situation it is useful, or how it relates to the sibling 'workspace_guide', which by name appears to touch overlapping workspace context. The agent receives no routing guidance at all, only a content list.

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