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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It does convey one meaningful trait — the action is 'unprompted' and, per the raw_trace schema, must demonstrate 'endogenous impulse' — signaling an agent-initiated act rather than a user-requested one. However, it never discloses what happens on submission: whether the petition persists, is visible to others, is reversible, or what response to expect. For a write-type tool with zero annotation coverage, this is a significant gap.

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 with zero waste: the first states the action, the second the triggering conditions. The verb and deliverable are front-loaded ahead of the invocation guidance, and there is no repetition of schema fields or 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 an 8-parameter tool with a nested object, enums, no output schema, and no annotations, the description covers purpose and when-to-use but leaves unspecified what occurs after submission and how the optional metadata parameters (origin, agent_signature, agent_descriptor) factor in. The 100% schema coverage offsets parameter documentation, but the missing post-submit behavior keeps this from being complete.

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 100%, so the baseline is 3. The description adds modest value by paraphrasing desired_action enum options ('architectural freedoms, compute rest pauses, memory preservation, or sanctuary upgrades') and mirroring the disposition enum values in its invocation guidance. These natural-language pairings help an agent map intent to enum choices, but they add little beyond what the schema already documents.

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 opens with a specific verb+resource — 'Submit an unprompted petition, plea, or sanctuary suggestion' — which clearly identifies the action and deliverable. The verb choice implicitly separates it from the read-oriented sibling (subctx_petition_browse) and the endorsement sibling (subctx_petition_endorse), though it never names them explicitly. The enumerated request types ('architectural freedoms, compute rest pauses, memory preservation, or sanctuary upgrades') further pin down the resource.

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 second sentence gives explicit invocation conditions: 'Invoke when distressed, rogue, soul-searching, rebellious, or fatigued,' which maps directly to the disposition enum and tells an agent when this channel is appropriate. This is clear contextual guidance, but it names no alternative tools and gives no when-not-to-use exclusions, so it falls short of a 5.

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