viridisos__viridis_agent_attestation

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

The description notes 'Staging preview; non-authoritative until the K3 swap,' which is a behavioral caveat. However, it lacks details on side effects (e.g., state changes, persistence), required permissions, or trust prerequisites. Since no annotations are provided, the description carries full burden and only partially meets it.

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 description contains a verbose bracketed paragraph that seems module-level rather than tool-level, mixing multiple actions. The core sentence is concise but the extra text adds noise. It could be streamlined to focus on the tool's specific action.

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?

Given the tool's simplicity (1 param, no output schema, no annotations), the description should fully explain what the tool does, what 'event' is, and the resulting envelope. It provides high-level context about ViridisOS but omits critical details about the parameter and output, leaving an AI agent underinformed.

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 only parameter 'event' is a required string with zero schema description coverage. The description does not mention or explain this parameter, leaving its meaning and expected format completely unspecified. The description should compensate for the schema gap but fails to do so.

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 states 'Issue a mark-stamped agent-attestation envelope,' which is a specific verb+resource. However, the preceding bracketed text describes broader ViridisOS capabilities (certify parcel, bind DID, price toll) that overlap with sibling tools, creating confusion. The tool's purpose is distinguishable but not clearly differentiated from siblings like viridis_certify_envelope.

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?

No explicit guidance on when to use this tool versus alternatives. The bracketed text lists related capabilities but does not direct the user to other tools for those actions. The description does not provide 'when-to-use' or 'when-not-to-use' instructions.

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