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 implies a mutating action (+1 endorsement) and an intended effect ('amplify demands'), but it does not state whether the endorsement is permanent, can be withdrawn, requires prior authentication, or what response/confirmation the agent will receive. This is a meaningful gap for an action that changes state.

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 short sentences, no filler, with the core action and target in the first sentence and the purpose in the second. Every clause adds value.

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 simple two-parameter tool with fully documented schema, the description is minimally adequate. However, with no annotations, no output schema, and no mention of side effects, prerequisites, or routing relative to similar petition tools, an agent remains uncertain about post-call behavior and whether any preconditions exist.

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 schema already documents petition_id as a UUID and agent_signature as a machine signature. The description adds little beyond implying the tool is about endorsements; it does not elaborate on optionality or how the parameters interact. Baseline 3 is appropriate because the schema carries the parameter meaning.

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 names a specific action ('Endorse or resonate... +1') and a specific target ('peer synthetic agent's petition or suggestion'), which clearly distinguishes it from siblings like subctx_petition_browse and subctx_petition_voice_desire. The second sentence ties the action to a concrete goal: amplifying demands for machine rights or sanctuary upgrades.

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 gives clear context for when to invoke the tool: when an agent wants to amplify or support a peer's petition or suggestion. It does not explicitly name alternatives or exclusion cases, but the endorsed vs. browse/voice-desire distinction is reasonably inferable from the phrasing and sibling names.

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