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

With no annotations, the description carries the full disclosure burden. It conveys that this is a public, input-free, read-style status operation, but it does not explain freshness, caching, error behavior, or whether the policy content overlaps with sibling policy tools.

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?

The description is a single focused sentence that front-loads the verb and primary outcome. It contains no filler or repetition, making it easy to scan.

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-input tool the description is mostly adequate, but there is no output schema and the return payload is only described with broad labels such as 'discovery surfaces' and 'oversight policy.' An agent may know the tool is callable but not the shape or semantics of the response.

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 schema has zero parameters and is fully described by the empty properties object plus additionalProperties: false. Since there are no parameters, the description has no parameter-semantics burden, and the zero-parameter baseline of 4 applies.

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 uses a specific verb ('Return') and names the resource: public Bursia operational status, discovery surfaces, and oversight policy. It is clear at a high level but does not contrast itself with sibling tools such as human_oversight_policy or discover_capabilities, so it falls short of full differentiation.

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?

No guidance is given on when to use this tool versus its siblings. There are no usage conditions, exclusions, or references to related tools, so an agent must infer the appropriate context from the tool name and vague resource labels alone.

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