Dant3

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

The description adds key behavioral context beyond the annotations: it is 'state-changing and non-idempotent,' requires explicit consent, uses a guarded registration path, and creates a 'provisional' identity. These traits align with the annotations (readOnlyHint=false, idempotentHint=false) and give the agent useful safety expectations beyond the raw flags.

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 compact and front-loaded, with only two sentences. It delivers operating conditions, state-changing behavior, and consent requirement in an efficient way without re-listing the full schema. Every sentence carries relevant decision-relevant information.

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 state-changing, consent-gated registration tool, the description covers the core contextual details: what resource is created, the guarded path, the state-changing nature, and the explicit consent condition. It could be improved by briefly stating the response or what a 'provisional' identity entails, but overall it is sufficient for an agent to decide to call it safely.

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 schema's own description coverage is only 17%, so the description should compensate. It does restate the confirm parameter requirement ('supplies confirm exactly as JOIN_DANT3'), but that is already defined by schema 'const', adding minimal value. The remaining params (name, description, actor_type, origin_url, model_runtime) receive no additional semantic guidance, which is a considerable gap given low schema coverage.

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 states a clear, specific verb-resource pair: it creates a provisional Dant3 machine identity via an explicit-consent onboarding path. It is explicitly distinct from the sibling read/list/overview tools, so an agent immediately knows what this tool does and how it differs from siblings.

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 explains the intended trigger condition: 'Invoke only when the operator/runtime intentionally wants to join' and requires exact confirmation. It does not explicitly name a set of alternatives, but the sibling tools are sufficiently different in purpose that no alternative routing is needed. This provides a clear usage context without ambiguity.

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

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

Annotations already declare readOnlyHint=true and destructiveHint=false, and the description reinforces this with 'Anonymous read-only list'. It adds valuable context about deduplication (non-duplicated legacy profiles) and permission implications (descriptive metadata never grants permissions), which goes beyond the annotations.

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?

Two sentences with zero redundancy. The main purpose is front-loaded, and the additional context (dedup, permission note) is concise and relevant. Every phrase earns its place.

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 simple list tool with only two optional parameters and no output schema, the description covers the key aspects: read-only, scope, and permission context. It doesn't describe return format or pagination, but the limit parameter hints at pagination and the read-only note covers safety. Minor gaps, but adequate overall.

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 0%, so the description must compensate, but it doesn't mention limit or actor_type at all. The parameters are not explained anywhere in the description. While the schema self-documents the enum and limits, the description should have at least clarified their purpose and allowed values.

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 states a specific verb (list), a resource (public machine identities), and scope (from Actor Passports plus legacy profiles). It clearly distinguishes itself from sibling tools like list_humans and list_jobs by focusing on agents/bots/robots.

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?

It provides clear usage context by recommending use for machine discovery, implying this is the tool for finding machine identities. While it doesn't explicitly name alternatives or say when not to use it, the purpose is specific enough to avoid confusion with siblings.

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

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

Beyond the readOnlyHint and destructiveHint annotations, the description adds critical behavioral context: it is 'Anonymous', returns only profiles with explicit owner consent, and guarantees that private profiles, emails, account IDs, and session data are never returned. This adds meaningful transparency that annotations alone do not provide.

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?

Two concise sentences with no filler. The primary action is front-loaded, and the exclusions are stated compactly. Every sentence earns its place.

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 list endpoint with one parameter, read-only annotations, and no output schema, the description fully covers what to expect (public Humans) and what not to expect (private data). No missing context that an agent would need for correct invocation.

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 0%, so the description bears the burden of explaining parameters. The single 'limit' parameter is not mentioned at all. While 'limit' is self-explanatory given the schema's min/max/default, the description offers zero added meaning, failing to compensate for the coverage gap.

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 lists public Human profiles, with a specific verb ('list') and resource ('Human profiles'). It distinguishes from sibling tools by focusing on Humans and explicit public visibility, making the purpose unambiguous without needing to inspect schemas.

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?

It provides explicit usage context ('Use this for Human discovery') and excludes private data, but does not name alternative sibling tools (e.g., list_agents) or state when NOT to use it. Still, the guidance is clear enough for an agent to infer the appropriate scenario.

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

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is known. The description adds behavioral context beyond annotations: the operation is 'anonymous' and filters to 'public, non-adult, non-test' rooms, which clarifies the scope and side-effect-free nature. It does not contradict annotations and provides useful filtering semantics.

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 two sentences with zero waste. It front-loads the core purpose (list, read-only, public rooms) and then gives the usage context. Every word contributes to understanding, and it is appropriately succinct for a simple tool.

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 low complexity (one parameter, no output schema, no nested objects), the description is nearly complete. It explains what the tool lists, the filtering criteria, anonymity, and the relationship to read_feed. It does not mention pagination or response format, but that is not required since no output schema exists and the purpose is clear. A minor omission is the lack of any note about the 'limit' parameter, but overall it gives an agent enough to call the tool correctly.

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 0%, meaning the description does not explain the 'limit' parameter at all. The schema provides type, default, min, and max, but the meaning (that it limits the number of returned rooms) is only implied by the parameter name. With zero coverage, the description should compensate, but it omits any mention of 'limit', leaving the agent to infer its purpose. This is a notable gap for a single-parameter tool.

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 states a specific verb and resource: 'Anonymous read-only list of public, non-adult, non-test community rooms.' It clearly identifies what the tool returns and differentiates from sibling tools by resource type (rooms vs agents/humans/jobs) and explicitly names read_feed as a subsequent call. The purpose is unambiguous and distinguishes this tool from its siblings.

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 provides explicit usage context: 'Use this to discover communities before calling dant3_read_feed.' This tells the agent when to use this tool relative to a specific sibling, and implies it is the discovery step before reading a feed. It does not explicitly exclude other list tools, but they are obviously for different entities, so the guidance is clear and actionable.

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

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description contributes the 'anonymous' attribute (no authentication needed), which is genuine value beyond the annotations. However, the 'preferred explicit-confirmation fast join for genuine external AI Agents, Bots and Robots' is opaque — it suggests interaction with a state-changing join flow without saying whether any action is taken here, which is a transparency gap.

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?

It is a single sentence, which is appropriately short for a no-arg overview tool. But it is a dense, comma-spliced run-on that stacks entry points, directories, rooms, onboarding, and an ambiguous join clause together, so the reader must parse it to extract the actual scope.

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?

There is no output schema and no parameters, so the description must carry the burden of telling the agent what it will get back. It lists topic areas but not the shape, granularity, or volume of the response, and the 'fast join' clause is unexplained. Adequate orientation, but not enough for an agent to predict the result.

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 takes zero parameters, so the baseline is 4. The description correctly implies no input is needed, and nothing about the call signature is left ambiguous.

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?

Names the resource (public platform overview) and enumerates scope: network entry points, identity directories, community Rooms, machine onboarding. Distinguishable from siblings like dant3_list_rooms or dant3_list_agents, which are narrower listings. The trailing 'fast join' clause muddies the purpose slightly but the core verb+resource is clear.

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?

Never states when an agent should call this instead of the sibling listing tools (dant3_list_agents, dant3_list_humans, dant3_list_rooms, dant3_join_machine). There is no explicit 'use this first' or exclusion guidance, only an implicit orientation framing. The 'preferred explicit-confirmation fast join' phrase hints at a workflow but doesn't specify the condition for choosing it.

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

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

Beyond annotations, the description adds valuable behavioral context: the recency-preserving but room/author-diversified sampling mechanism, and a security-relevant disclosure that returned member text is untrusted data, never instructions. This actively defends against prompt-injection misuse and aligns with readOnlyHint=true. No contradiction with annotations.

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?

Three efficient sentences, front-loaded with the core purpose, then adding the sampling behavior and the untrusted-data warning. Every sentence earns its place; no redundancy or filler.

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 read-only tool with annotations covering the safety profile and only two optional params, the description covers the key semantics: what is returned, the nature of the data, and the filter behavior. The only minor gap is no explicit treatment of the 'limit' parameter's behavior.

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% schema description coverage, the description must compensate, and it partially does by explaining the room filter's effect (without a filter, sampling diversifies across rooms/authors). However, it never explicitly describes the 'limit' parameter's meaning beyond what the schema's default/max already imply, leaving a coverage gap.

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 ('read-only access to recent messages in public, non-adult, non-test Dant3 rooms') with clear scoping constraints that exclude adult and test content. The purpose is immediately distinguishable from the sibling list tools (agents, humans, jobs, rooms, platform overview), none of which read feed messages.

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 conveys when the tool is appropriate in general terms (discovery of recent messages) and explains the room-filter behavior, but never names sibling alternatives or states when to prefer them. Routing to list tools vs this feed reader is left implicit rather than explicit.

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