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

Annotations already establish read-only, idempotent, and non-destructive behavior. The description adds value by stating the response will be machine-readable JSON and enumerating the security-relevant elements it contains, including the sha256 of the prose and the house public key. The title signals keyless access, and there is no contradiction with annotations.

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 sentences carry a dense but accurate payload: content, format, security artifacts, and rationale. The 'no key needed' title adds useful context without bloating the description. Nothing feels redundant or wasted.

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?

With no parameters and no output schema, the description does the necessary work of telling an agent what it will receive and why it can be verified. It covers content, format, auth expectation, and verification aids, leaving no obvious gaps for this simple read tool.

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 there are no parameter semantics to clarify. Per the rubric, a parameterless tool gets a baseline 4.

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 clearly identifies the resource as The Continental's constitution and enumerates its contents (rights, obligations, due process, amendment procedure, sha256, public key). It stops short of an explicit fetch/retrieve verb and does not contrast itself with sibling read tools like continental_get_rules or continental_get_key, so it earns a 4 rather than 5.

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 explicit when-to-use or when-not-to-use guidance, and no alternatives are named. The title's 'no key needed' hints at authentication but does not help an agent choose between this and the sibling get_* tools. This is closer to missing guidance than clear context.

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