get_trust_boundary

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

With no annotations provided, the description minimally discloses behavior by stating what is returned (passes set), but omits side effects, authentication needs, or whether it is read-only.

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 a single efficient sentence front-loading the action, but lacks structural elements like bullet points or sections.

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?

The output schema partially compensates for return value explanation, but the description fails to detail all parameters (especially 'server_version') and omits error conditions or prerequisites.

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 67% (two parameters described), but the tool description adds no additional meaning beyond the schema and does not cover the undocumented 'server_version' parameter.

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 it retrieves a single trust boundary and specifies inclusion of the 'passes' set, distinct from sibling tools that create, edit, or remove trust boundaries.

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 retrieval use but does not provide explicit when-to-use or when-not-to-use guidance, nor mentions alternatives among many sibling tools.

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