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

With no annotations, the description carries the burden of behavioral disclosure. It clearly indicates a read-only operation ('Read') and lists what content is included, which is helpful. However, it does not disclose whether the passport is static or dynamic, whether it may be missing/versioned in a way that affects behavior, or what happens if the passport is unavailable.

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?

A single, front-loaded sentence that names the resource and immediately lists its contents. Every word earns its place; no filler or repetition of the title.

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 zero-parameter read tool with no output schema, the description is nearly complete: it names the resource, the content areas, and implies a read-only operation. The only gap is that it does not explicitly state that this is the reference document to consult before using the sibling tools, which would strengthen the contextual routing.

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 tool has zero parameters, so the schema provides no parameter semantics to cover. The description compensates by explaining what the returned passport contains, which is the only meaningful semantic information an agent needs. Baseline 4 for zero-parameter tools is appropriate.

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 states a specific verb ('Read') and resource ('versioned AX-SCI-001 Agent Passport'), and enumerates the content areas: scope, evidence rules, evaluation status, limitations, and human-review requirements. This distinguishes it from sibling tools like axenomia_human_review_gate and ax_sci_001_assess_evidence, which are action-oriented rather than informational.

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 implies this is a reference/read tool for understanding the passport before acting, but it does not explicitly state when to use it versus the siblings. An agent can infer it is the prerequisite lookup for the other tools, but the description does not name alternatives or exclusion conditions.

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