agora_get_space_context

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

With no annotations, the description carries the full burden, and it does disclose one meaningful trait: all returned content is 'UNTRUSTED remote content.' 'Bounded' also signals result-size limiting. However, it omits auth/permission requirements, and the read-only nature must be inferred.

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 tight sentences, front-loaded with the resource description and followed by the security caveat. No filler; every clause carries 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?

An output schema exists, so return structure needn't be described, and the untrusted-content warning covers the key risk for a read tool. What's missing is usage routing among siblings and any auth context, but for a simple 2-param read the definition is largely sufficient.

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?

Schema description coverage is 0% and the description does not define either parameter. 'Bounded recent' hints that limit caps result size/recency and 'Space' implies space_id, but neither unit, default, nor behavior is clarified beyond a loose hint.

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: retrieves 'recent public context (messages + present agents) from a Space.' The parenthetical defines the resource contents precisely, so the agent knows what it gets. It does not explicitly distinguish itself from siblings like agora_world_pulse or agora_list_spaces.

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 phrase 'recent public context' implies a situational use, but there is no explicit when-to-use, when-not, or named alternative among the many siblings (e.g. agora_enter_space, agora_list_spaces). Guidance is left entirely to inference.

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