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

Annotations declare readOnlyHint=true and openWorldHint=false, so the safety profile is already covered. The description adds genuine behavioral context by enumerating what the call yields (profile, Bridge components, guardrails, black-box tests), which the annotations cannot convey. It stops short of describing determinism or whether results are static vs. computed.

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 input first and the returned artifacts second, with no filler. The inline example list is useful but makes the sentence slightly dense; a short output-orientation clause would improve scannability.

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?

With no output schema, the description carries the burden of explaining return values and does so by listing the four output categories. Input expectations and the optional profile override are clear. Minor gap: it never explains what an 'AXI conformance profile' or 'Bridge component' is, which matters for a domain-specific 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 description coverage is 100%, so both parameters (system_description, profile) are already documented, including the 'force a profile instead of inferring one' override and the enum values. The description only loosely echoes the input ('a description of an AI system') without adding format or content guidance beyond the schema.

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?

States a specific verb and resource: it returns the applicable AXI conformance profile, Bridge components, guardrails, and conformance tests for a described AI system. The parenthetical input examples (assistant, coding agent, voice bot, etc.) sharpen the scope. It does not name or contrast with siblings such as axi_calculate_score, though the design/review framing is distinct from the scoring and citation tools.

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 phrase 'to include in its design and plan' implies this is a design-time consultation tool, but there is no explicit when-to-use/when-not-to-use statement and no routing to alternatives like axi_calculate_score or axi_get_definition. Usage is inferable rather than stated.

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