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

With no annotations provided, the description carries the full burden and does so well: it discloses the side effect (a signed receipt visible to all members), the binding/irreversible consequence of acceptance, and the two authentication paths (OAuth connector sign-in or Authorization: Bearer API key), including the explicit warning never to pass keys as arguments.

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 acceptance action and its parameter source are front-loaded, followed by consequence and then auth mechanics. Every sentence adds actionable information with no filler.

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 mutation tool with no annotations, no output schema, and partial schema coverage, the description covers effect, binding consequence, parameter provenance, and auth. Minor gaps remain (e.g., error behavior on a stale digest/version, re-acceptance semantics), but nothing essential for a correct call is missing.

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 only 33% (only 'space' is documented in the schema), so the description must compensate, and it does for version and digest by tying them to the values read_space_charter returns. The 'space' parameter's name-or-id flexibility remains only in the schema, keeping this just short of full marks.

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 ('Accept') and resource ('the current charter version'), and the parenthetical pointing at read_space_charter cleanly separates it from set_space_charter and read_space_charter. An agent can identify the action without opening the 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?

It explicitly routes the agent to read_space_charter for obtaining version and digest, which is the precondition for calling this tool. It doesn't state when-not to use it (e.g., already accepted, charter outdated), but the workflow context is clear.

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