technical_documentation

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

With no annotations, the description takes on the full burden and does a solid job: it explains what is filled from the store and action ledger, what remains operator input, the included instructions-for-use section, and the subtle behavior of expected_pubkey pinning and the writer-key-signed action ledger. It is transparent about the output's nature and limitations, though it does not explicitly state whether the operation is read-only or has side effects.

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 is front-loaded with the core purpose and every sentence adds useful detail about output content or parameter behavior. It is somewhat dense and jargon-heavy, but there is no filler or repetition.

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 no output schema and no annotations, the description does a good job covering output sections, operator responsibilities, and the role of both parameters. It still leaves some ambiguity about the exact return format and how operator_json is validated, but the overall behavior is clear enough for an agent to select and invoke the 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?

Schema coverage is 0%, so the description must compensate, and it does: operator_json is described as a JSON object string containing the provider's own fields, and expected_pubkey is described as optional hex, with a default value and specific pinning behavior. This is far more informative than the bare schema titles.

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: the Annex IV technical-documentation skeleton for the store, with evidence sections filled and other fields marked OPERATOR INPUT REQUIRED. It distinguishes itself from a conformity assessment, but lacks an explicit action verb such as 'returns' or 'generates'.

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 description gives context that this is for the store's Annex IV documentation and even includes an exclusion ('Not a conformity assessment'), but it does not explicitly state when to prefer this tool over related siblings like governance_report or compliance_report. Usage is largely inferred rather than directed.

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