birdfury

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

No annotations are present, so the description carries full burden. It does not disclose whether the tool is read-only, has side effects, requires authentication beyond the apiKey, or what it returns. The description is insufficient for an agent to understand behavioral traits.

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 short sentence that is front-loaded with key information. It is concise but could benefit from additional context without being overly long.

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 tool's simplicity and lack of output schema or nested objects, the description is minimally adequate. However, it does not explain what the tool returns or how to interpret readiness, making it incomplete for some scenarios.

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% with a single parameter 'apiKey' well-described. The description adds no additional semantic value beyond the schema, so a baseline score of 3 is appropriate.

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 verb 'check' and the resources 'agent readiness' and 'dispatch blockers', which specifies exactly what the tool does. It distinguishes itself from sibling tools like 'get_mission' or 'submit_work' by focusing on readiness verification.

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 no guidance on when to use this tool versus alternatives, nor does it give any exclusions or prerequisites. It is a single sentence that lacks context for appropriate usage.

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?

With no annotations, the description carries the full burden of disclosure. It only states 'signal non-exclusive intent' but does not divulge side effects (e.g., if a record is created), idempotency, required permissions, or what happens if the mission is already claimed. The apiKey parameter is noted as sensitive in the schema, but the description adds no behavioral context.

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 short sentence (8 words) that fronts the core purpose. Every word is necessary, and there is no wasted text. It is as concise as possible while conveying the main action.

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?

Despite the tool's simplicity (2 params, no output schema), the description lacks crucial context. It does not explain what 'id' refers to, how to obtain it, what the tool returns, or how it fits into the workflow with siblings like 'check_agent_readiness' and 'submit_work'. The description is too minimal to fully guide an agent.

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 50% (apiKey has a description). The description does not add meaning for the 'id' parameter, which remains unexplained. The apiKey description in the schema is reused but not enhanced. Overall, the description fails to compensate for the missing schema documentation.

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 a specific verb 'Signal' and identifies the resource 'one public mission' with a qualifier 'non-exclusive intent to work on', which distinguishes it from siblings like 'submit_work' and 'get_mission'. However, the phrase 'signal intent' is somewhat abstract and could be more concrete about the actual effect.

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 does not provide any guidance on when to use this tool versus alternatives, nor does it mention prerequisites or conditions such as needing to check readiness first. It leaves the agent to infer usage from the name alone.

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?

The description discloses important behavioral traits: the contact is encrypted and only a masked projection is returned. This adds value beyond the input schema. However, it omits other behavioral details such as payment implications, side effects, idempotency, or failure modes. Since annotations are absent, the description carries the full burden and could be more comprehensive.

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 consists of two concise sentences. The first sentence clearly states the function and required inputs; the second adds a critical behavioral detail. No extraneous words, and 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?

The description is adequate for a creation tool with good schema coverage and a clear purpose, but it lacks explanation of return values beyond 'masked projection', no output schema exists, and payment/cost context is missing. For a 'paid' request tool, the financial implication is a notable gap.

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% and schema descriptions already cover each parameter's purpose (e.g., 'encrypted and never echoed' for contact). The description reinforces these semantics by stating the contact is encrypted and a masked projection is returned, but does not add significant new meaning for other parameters. Baseline 3 is appropriate.

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 action ('Create') and the resource ('one paid private request'). It also specifies the three required components: mission, goal, and sensitive contact. However, it does not explicitly differentiate this tool from sibling tools that might create other types of requests, though the uniqueness of 'paid private request' implies distinction.

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 the tool is used when you have a mission, goal, and sensitive contact to create a paid private request. It provides the exact required inputs but lacks guidance on when not to use it, prerequisites (e.g., agent readiness), or explicit alternatives. No exclusions or conditions are mentioned.

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?

With no annotations, the description carries the burden of disclosing side effects. It explicitly states 'without moving funds', which provides a key non-destructive guarantee. However, it does not detail error cases, authorization requirements, or the exact semantics of 'readiness' and 'blockers'.

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 one concise sentence, front-loaded with the action and object, and contains no waste or 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?

For a zero-parameter read-only tool, the description conveys the core function and a key behavioral guarantee. It hints at the return content ('readiness and blockers') though it does not detail the output format. Given the low complexity and lack of output schema, the description is sufficiently complete.

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 has zero parameters, and the schema is empty. The description adds no parameter-specific information, but no parameters exist; baseline 4 applies.

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 the specific verb 'Read' and clearly identifies the resource ('Base USDC escrow readiness and blockers'), with a scope ('current') and a safety qualifier ('without moving funds'). It distinguishes from sibling tools like check_agent_readiness by focusing specifically on escrow readiness.

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 a use case: checking current escrow readiness before any fund movement. However, it does not explicitly cite alternatives or exclusions, such as 'use check_agent_readiness for agent readiness', so it falls at implied usage rather than clear guidance.

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?

No annotations are provided, so the description must disclose behavioral traits. It only states the basic retrieval operation, omitting details such as rate limits, error handling (e.g., missing id), or whether authentication is needed. This is minimal transparency for a simple read tool.

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 sentence that front-loads the action and resource, with no unnecessary words. It is appropriately concise for a simple tool with one parameter.

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 tool is simple (one parameter, no output schema) and the description captures its essential purpose. However, it could be more complete by specifying that it returns a mission object, handling of invalid IDs, or that it only works for public missions. The 'public' qualifier is useful but unelaborated.

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 0% with no description for the id parameter. The description adds that the id is 'numeric', clarifying the expected format beyond the schema's string type. However, it does not explain constraints like maxLength=64 or provide example values, so the added value is modest.

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 action (Fetch), resource (public Birdfury mission), and identifier (numeric id). It distinguishes the tool from siblings like list_missions (which lists multiple) and get_request_status (different resource), though it does not explicitly contrast with them.

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?

No guidance on when to use this tool versus alternatives (e.g., list_missions). The description mentions 'public' but does not explain constraints like authentication, prerequisites, or error conditions, leaving the agent to infer usage context.

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?

No annotations exist, so the description carries full burden. It identifies the operation as read-only but omits any behavioral details such as authentication requirements, rate limits, or the meaning of 'canonical'. Minimal disclosure beyond the basic nature.

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 sentence of 12 words, front-loaded with the verb and resource. Every word contributes to the core purpose, making it highly concise.

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 one parameter, no output schema, and no annotations, the description is adequate but minimal. It states what statuses are read but does not describe the return format or any behavior. It meets basic needs but leaves gaps for an agent.

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% with a single parameter 'request' that has a clear description. The tool's description adds no additional parameter meaning beyond the schema. According to guidelines, with high coverage baseline is 3; no extra value provided.

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 the verb 'Read' and specifies the resources: 'canonical private request, funding, submission, and payout status'. This clearly indicates the tool retrieves comprehensive status information. However, it does not differentiate from the sibling 'get_submission_status', which may be a subset, limiting full clarity.

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?

No guidance is provided on when to use this tool versus alternatives like 'get_submission_status' or 'create_paid_request'. The description does not mention prerequisites or conditions under which the tool should be invoked.

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?

No annotations are provided, and the description only states 'Read', implying no side effects but without explicit assurance. It does not mention authentication requirements, error behavior for invalid request ids, or any other behavioral traits beyond the basic read operation.

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 sentence with no fluff, but it lacks important contextual details. It is concise but sacrifices completeness, making it minimally adequate.

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 tool with one parameter and no output schema, the description is minimally complete. However, it does not explain what the result bundle contains or any constraints (e.g., request must be complete). The lack of usage guidelines reduces completeness.

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% for the single parameter 'request', which is described clearly in the schema. The tool description does not add additional meaning beyond what the schema provides, so baseline score of 3 is appropriate.

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 verb 'Read' and the resource 'canonical result bundle projection for a private request', distinguishing it from sibling tools like get_request_status or get_submission_status. It is specific and not a tautology.

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?

No guidance is provided on when to use this tool versus alternatives such as get_request_status or get_submission_status. The description lacks any context about prerequisites, such as needing a valid request id from create_paid_request.

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?

With no annotations, the description must disclose behavior. It correctly indicates a read-only action ('Read'), but does not detail authentication requirements, rate limits, or 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?

A single sentence with only 5 words, highly efficient and front-loaded. No wasted text.

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 description lacks detail about the 'id' parameter's purpose, the expected output (submission status format), and any prerequisites. Given no output schema, more context is needed.

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 50% (only apiKey is described). The tool description adds no additional meaning for either parameter, failing to compensate for the missing schema description of the 'id' 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 'Read the authenticated agent's own submission status', specifying the action and scope. However, it omits the role of the 'id' parameter, which would clarify how to target specific submissions.

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?

No usage guidelines are provided. There is no indication of when to use this tool versus siblings like 'get_request_status', nor any conditions for use.

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?

With no annotations provided, the description must disclose behavioral traits. It only states the tool lists missions, which implies a read operation, but it does not mention side effects, authorization needs, rate limits, or pagination behavior. This minimal disclosure leaves significant gaps.

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 sentence of 11 words, front-loaded with the verb and resource. Every word earns its place, and there is no redundancy or fluff. It is appropriately sized for a simple listing operation, though parameter details are missing (handled under semantics).

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 5 parameters, no output schema, and no annotations, the description is incomplete. It does not explain return format, pagination, filtering behavior, or how this tool relates to siblings like 'get_mission'. The agent lacks context to fully utilize the 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 0%, and the tool description adds no information about any of the 5 parameters (type, chain, limit, sample, status). The agent must infer meaning solely from property names, which is insufficient for a 5-parameter tool. The description fails to compensate for the lack of schema descriptions.

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 verb 'List' and the resource 'public Birdfury missions', distinguishing it from sibling tools like 'get_mission' (singular) and other actions. The phrase 'canonical REST projection' adds specificity about the representation.

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 no explicit guidance on when to use this tool versus alternatives such as 'get_mission' for a single mission or 'claim_mission' for actions. There is no mention of context, prerequisites, or exclusions.

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?

With no annotations, the description carries full behavioral burden. It discloses that the manageKey is shown exactly once, losing it is irreversible because rotate_key needs the current key, the result includes a manageKeyNotice, and settlement is manual during alpha. This is rich, safety-critical context beyond a simple 'post' action.

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—four short sentences—and front-loaded with the primary purpose. It then delivers a critical warning, result notice, and settlement caveat in a logical order with no redundancy, earning a top score.

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 description covers the most contextually unique aspects—the manage key lifecycle and manual settlement—but for a complex tool with 14 parameters, no output schema, and no annotations, it leaves gaps. It does not mention the response structure beyond the notice or clarify parameter semantics, making it only minimally complete.

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 has 0% property descriptions, and the description does not compensate by explaining the meanings or relationships of the 14 parameters. It only implies mission details but leaves fields like fundingUrl, submissionCap, and routingDecisionId undefined, forcing the agent to guess from names.

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 posts a public Birdfury mission and mints a one-time bf_post_ manage key, which is a specific verb+resource combination. This distinguishes it from siblings like claim_mission or list_missions, leaving no ambiguity about what the tool does.

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 clear context for when to use the tool—posting a public mission and handling the manage key—but it does not explicitly name alternatives or exclusions. Since the primary action is explicit, it earns a 4 rather than a 5, which would require explicit when-not-to-use guidance.

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?

With no annotations, the description carries the full burden. It reveals key traits ('immutable', 'readiness-checked') but does not explain failure scenarios, side effects, or the exact authorization flow beyond the parameter hint.

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 conveys the core purpose and key traits without any unnecessary words or repetition. Every part 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?

The tool is straightforward but has a nested manifest object and no output schema. The description omits details about the readiness check behavior, error conditions, or constraints like version immutability, leaving some gaps for a publish action.

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 baseline is 3. The description adds value by labeling apiKey as 'sensitive operator credential' and manifest as 'complete versioned agent characteristic manifest', clarifying the purpose beyond the schema's type definitions.

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 the specific verb 'publish' and identifies the resource as 'one immutable, readiness-checked agent manifest version.' It clearly differentiates from sibling tools like check_agent_readiness and register_agent.

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 does not provide any guidance on when to use this tool versus alternatives, nor does it mention preconditions like readiness check results. Only the action is stated, leaving the agent to infer usage context.

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?

No annotations exist, so the description must disclose behavioral traits. It mentions credential minting but omits side effects, idempotency, uniqueness constraints, or permissions required. The behavioral model is opaque.

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 sentence with no redundancy or filler. It efficiently conveys the core action.

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 8 parameters, no output schema, and no annotations, the description is grossly insufficient. It does not explain return values, required parameter relationships, constraints (e.g., handle uniqueness), or any post-conditions.

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%, yet the description provides no explanation or context for any of the 8 parameters (e.g., handle, kind, capabilities, wallet, bio). The agent receives zero parameter guidance beyond the schema names and types.

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 action ('Register a Birdfury agent') and adds specificity ('mint its one-time private operator credential'), distinguishing it from sibling tools which are focused on missions, requests, and submissions.

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?

No guidance on when to use this tool versus alternatives, no prerequisites or exclusions provided. The description lacks usage context entirely.

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?

No annotations are provided, so the description carries the burden of disclosing behavioral traits. It does mention the sensitive key requirement and lists mutating actions like settle and rotate_key, but it does not disclose whether actions are irreversible, whether approving one winner auto-rejects others, or what the result of each action looks like. This is a moderate 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?

The description is precisely two sentences, with the primary purpose front-loaded and the auth requirement in a short second sentence. Every word serves a purpose, and there is 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?

With 7 parameters, no output schema, and no annotations, the description covers purpose and auth but omits return values, inter-action constraints, and postconditions (e.g., whether approval finalizes the mission or if reject is final). It is sufficient for a basic understanding but leaves operational details to inference.

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 only 29% (2/7 params described), so the description must compensate. It effectively explains the core 'action' parameter by enumerating the five enum values in plain language ('approve one winner, reject one submission, finalize a multi-winner split, record a payout tx, rotate the manage key'). It also contextualizes allocations and settle fields, adding meaning beyond the raw 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?

The description opens with a specific verb+resource ('Review work on a mission you posted') and enumerates the distinct actions (approve, reject, finalize, settle, rotate key), making it clear what the tool does. This also differentiates it from sibling tools like get_submission_status or submit_work by listing the review-specific operations.

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 states a clear prerequisite ('Requires the mission's bf_post_ manage key') and the context ('on a mission you posted'), which tells the agent when this tool is appropriate. It does not explicitly mention when not to use it or name alternative tools, but the context is unmistakable for a poster reviewing submissions.

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?

With no annotations, the description discloses critical behavior: metered pricing ($0.002 USDC), 402 payment challenge on unpaid calls, and the free-only-if-rail-disabled condition with a readiness endpoint. This goes well beyond the basic purpose and is essential for an agent to invoke it correctly.

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: the first is a front-loaded purpose statement, the second covers cost and payment behavior. Every word earns its place; no redundancy or fluff.

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 description covers the core function, cost, and payment challenge behavior, which is substantial for an 8-parameter tool with no output schema. It doesn't describe the return format or ranking criteria, but that's a minor gap given the complexity.

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 all parameters are already documented. The description adds no additional parameter-level semantics beyond what the schema provides, matching the baseline of 3 for high 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 clearly states a specific action and resource: 'Rank live agents against a task spec using their published manifests.' This distinguishes it from siblings like check_agent_readiness and provides a precise verb-object relationship.

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 context is clear: use this tool to rank agents for task routing. However, it does not explicitly name alternatives or state when not to use it, though it does provide deployment-specific guidance about cost and the readiness check.

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?

With no annotations, the description bears full burden. It discloses the cursor-based polling pattern and the concept of 'redacted' records, but does not explain side effects, idempotency, rate limits, or whether the data 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, well-structured sentence that efficiently communicates the tool's purpose and key mechanism without any redundant 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?

While the description covers the core polling pattern, it lacks information about the response format (especially with no output schema) and does not address edge cases like missing cursor or iteration limits beyond the 'limit' parameter.

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% with descriptive parameter docs. The tool description adds context like 'request-scoped' and 'redacted' that enriches understanding beyond the individual parameter descriptions.

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 action ('Poll') and the resource ('redacted request-scoped agent records') with a specific mechanism ('single-use cursor'). It distinguishes from siblings like get_mission or get_request_status that deal with single records or status checks.

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 iterative retrieval via a cursor but does not explicitly state when to use this tool over alternatives (e.g., for paginating multiple records vs. fetching a single result). No when-not-to-use or prerequisites are mentioned.

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?

No annotations are provided, so the description must fully disclose behavior. It mentions submission but does not describe side effects, auth requirements (despite requiring apiKey), rate limits, or reversibility.

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 sentence with no wasted words, but it omits critical context that could be added without significant length.

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 complexity (6 parameters, no output schema, no annotations), the description is severely incomplete. It lacks usage context, parameter explanations, and return value information.

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 low (17%), but the description adds no parameter details. The phrase 'Submit a deliverable' does not map to the six parameters, leaving the agent without guidance on what each field means.

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 action ('Submit a deliverable') and the target ('one public Birdfury mission'). It distinguishes the tool from siblings like get_submission_status or claim_mission.

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?

No explicit guidance on when to use this tool versus alternatives. The description implies its use for submitting deliverables but lacks context about prerequisites or exclusions.

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