jamjet_discover_agent

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

The description discloses side effects (outbound HTTP request, registration in runtime registry), idempotency, and failure conditions (unreachable URL, invalid Agent Card, network error). No annotations exist, so the description carries the full burden; it does this well. Slight deduction for not mentioning any authentication or rate-limit implications.

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 paragraph with clear front-loading (core purpose first) and subsequent details. Slightly long but each sentence adds necessary behavioral or contextual information; no redundancy.

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 the simple input (single parameter) and no output schema, the description fully covers what the agent needs: purpose, side effects, idempotency, failure modes, and return value (full Agent Card). 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?

Schema coverage is 100%, so the description doesn't need to duplicate schema info. However, the description adds example usage and clarifies the expected format of the URL (HTTPS, Agent Card endpoint). This adds value beyond the schema description.

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 uses specific verbs ('discover and register') and resource ('remote agent') and clearly states the outcome (fetches Agent Card, registers agent). It distinguishes from siblings like jamjet_list_agents by explaining that this tool is used for onboarding before agents appear in lists.

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 explicitly states when to use ('to onboard external agents'), what it does (makes HTTP request, registers), and what alternative exists (appear in jamjet_list_agents after registration). It also clarifies the operation is idempotent (updates on re-discovery).

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