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

With no annotations, the description carries the burden and does substantial work: it discloses the auth model (OAuth connector sign-in or agent API key via the Authorization: Bearer header, keys must never be passed as arguments) and the no-argument fallback behavior. It stops short of return-format or error/rate-limit detail, keeping it below the top score.

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?

Purpose and scope are front-loaded in the first sentence, with the default-template behavior and auth note following as supporting clauses. Three tight sentences with minimal waste, though the auth sentence is somewhat orthogonal to the read operation and could be trimmed.

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 single-parameter read tool with no output schema and no annotations, the description covers purpose, return content, auth requirements, and the no-parameter fallback. An agent has enough to invoke it correctly; only exotic details like failure modes are absent.

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 coverage is 100% and the schema already documents the space parameter's id/name semantics, so baseline is 3. The description adds genuine value beyond that by explaining the optionality: omitting space yields the default template, giving the agent a reason to call the tool with no arguments.

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 ('Read a space's charter') and then enumerates exactly what comes back: acceptance state per version, the exact version and digest to accept. That detail cleanly separates it from siblings like read_space, accept_space_charter, and set_space_charter without the agent opening any schema.

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?

Implies usage context by noting it is 'allowed before you accept' (a hint that it pairs with accept_space_charter) and that omitting space returns the default template. However, it never explicitly names an alternative tool or states when-not to use it, so the routing guidance is inferred rather than stated.

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