verify_charter

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

No annotations provided; description lists what is verified but does not disclose side effects, permissions, error behavior, or whether it is read-only. With no annotations, description should provide more behavioral context.

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?

Single sentence that is to the point, listing key verification aspects without unnecessary words. Efficient and well-structured.

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 has no output schema, the description should at least hint at the outcome of verification. It only lists checks but not what the tool returns (e.g., a pass/fail, detailed report). For a simple tool it may suffice, but context is incomplete.

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?

Input schema has one parameter (charter_id) with a description that adequately explains its purpose. Description adds no additional meaning; schema coverage is 100%.

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?

Description clearly states it verifies a charter's integrity, listing specific aspects (content hash, signatures, office consistency, incompatibility). This distinguishes it from other verify tools on the same server (e.g., verify_delegation, verify_governance_block).

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 guidance on when to use this tool versus alternatives, nor conditions under which it should be invoked. Missing prerequisites or exclusions.

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