discover

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

While no annotations are provided, the description thoroughly explains what the tool returns, including an example response. It implicitly indicates a read-only operation, though it could be more explicit about having no 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 well-structured with bullet points and an example, front-loading the purpose. It is slightly lengthy but each sentence adds value, making it appropriate for the complexity.

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 parameters and no output schema, the description provides a complete overview of the return structure, covering tools, auth methods, rate limits, etc. No gaps remain.

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?

With 0 parameters and 100% schema coverage, there is no need for parameter explanations. The baseline for 0 parameters is 4, and the description adds no misleading information.

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 the tool discovers AgentTrust capabilities, tools, auth methods, and rate limits. It uses a specific verb-resource pair and distinguishes itself from sibling tools by being the initial discovery endpoint.

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?

Explicitly says 'Call this first when connecting to AgentTrust' and notes 'No authentication required.' This provides clear when-to-use guidance and prerequisites.

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