GateCore Marketplace

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

Annotations already declare that the tool is read-only, idempotent, and non-destructive, and the description does not contradict them. The description adds useful behavioral detail: the results are governed marketplace capabilities containing machine-readable pricing, scopes, and trust terms, and the ordering preserves the marketplace's organic order. It does not cover pagination or result limits, but those are not required given the strong annotation coverage.

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 and contains no filler or redundancies. The core purpose is front-loaded, with the ordering guarantee in the second sentence adding meaningful behavioral information without extra 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?

For a read-only discovery tool with four optional parameters and no output schema, the description gives a useful high-level picture: listing-like results with pricing/scope/trust details and original ordering. However, it leaves out parameter semantics and sibling-tool distinctions, so the agent has enough to start but not enough to select filters confidently.

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 needs to compensate, but it barely does. 'minimum trust terms' and 'machine-readable pricing' hint at trust and price-related parameters, but tags, query, min_trust, and max_price_cents are not explained, including units, filtering behavior, or combinations. An agent would have to infer semantics from parameter 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 uses a clear verb ('Discover') and identifies the resource: governed GateCore marketplace capabilities, including machine-readable pricing, required scopes, and minimum trust terms. It conveys the type of data returned, though 'capabilities' is slightly abstract and it does not explicitly differentiate from sibling listing tools.

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 gives no explicit guidance on when to use discover_listings versus get_listing, list_procurements, or other siblings. Usage is only implied by the tool's name and general discovery wording, with no stated exclusions or alternative-selection criteria.

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, idempotentHint=true, and destructiveHint=false, so the description does not need much safety reporting. The description adds useful context by stating the listing is 'governed' and that terms are machine-enforceable, but it does not disclose any error or authorization edge cases. It is adequate but not rich.

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 entire description is one focused sentence that starts with the verb and resource, and then lists the specific terms it returns with a colon — no wasted words. It is structured well for quick agent scanning, missing all necessary.

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 fills the most critical gap by naming exactly which fields appear in the returned terms. It doesn't mention the success/failure envelope or a fallback like what to do if the listing does not exist, but with the overall built-in readOnly hint and the tool's simplicity, the description is complete enough for a correct call.

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 contains only listing_id with no description for it, leaving 0% schema description coverage. The description's 'Fetch one listing' is some compensation — it implies listing_id identifies the target — but it never actually explains the parameter or the expected value format. The tool name makes the self-evident, but the description itself adds minimal direct param meaning.

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 the exact resource (a governed marketplace listing) and carries a precise verb ('Fetch'), also limiting it to 'one' listing, which distinguishes it from discover_listings and other collection-based siblings. The enumeration of what it returns adds valuable specificity.

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 that this tool is correct when a specific listing is in-hand, since it fetches a single listing and its contract terms. However, it does not explicitly name alternatives or exclude cases such as searching/ discovering listings, so the usage context is inferred rather than spelled out.

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, idempotentHint=true, and destructiveHint=false. The description adds 'credential tenant' scoping and 'public modes' context but does not disclose return shape, ordering, pagination, or whether the result is a full list.

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?

One sentence, no filler. The action and resource are front-loaded, and the additional context is 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?

For a zero-parameter, read-only list operation with strong annotations, the description is nearly complete. It could be slightly clearer about what 'public modes' means and what the return contains, but the tool's core callable behavior is evident.

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?

There are zero parameters and schema coverage is 100%, so the description does not need to explain parameter meaning. This is a no-parameter tool, making parameter semantics a non-issue.

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') and resource ('procurement decisions') and adds useful scope ('credential tenant', 'public modes'). This clearly distinguishes it from sibling tools like procure or get_listing, which are action- or listing-oriented.

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 when-to-use guidance, exclusions, or alternatives are mentioned. The description implies this is a read-only list operation, but it never explains when the agent should choose this tool over siblings such as discover_listings or procure.

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 only say the operation is not read-only, not idempotent, and not destructive. The description adds meaningful behavior: identity from MCP access key, trust from GateCore's baseline, and a PROCURE/REVIEW/DENY outcome with delegation. This goes beyond the annotations and helps the agent predict behavior, though side effects are not explicitly stated.

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 front-load the core action and add only one compact sentence of behavioral context. There is no filler, and each clause adds information about mode, trust, or outcome.

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 no output schema and no parameter descriptions, this 6-parameter governance tool is under-specified. The description covers the decision categories and part of the auth model, but an agent still lacks parameter semantics, exact response shape, mode selection details, and error 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?

Schema description coverage is 0% and required fields like requester_trust, requester_agent_id, and scopes receive no explanation in the description. Saying 'procurement for a listing' only echoes the listing_id property and adds no semantic detail for the optional parameters or trust value.

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 verb and resource: 'Request governed procurement for a listing.' It also names the expected outcome (PROCURE, REVIEW, or DENY), which makes the tool's role distinct from the sibling read/list/lead tools. However, it does not explicitly name or contrast a sibling, so it stops short of a 5.

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?

There is no guidance on when to choose this tool over submit_lead or other siblings, and no stated conditions or exclusions. The phrase 'public full mode' hints at a mode distinction but does not explain when to use it or what alternatives exist.

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 provide no useful hints—all flags are false, so the description must disclose behavior. While it mentions 'consented' (a requirement), it does not explain whether the operation is a write, what happens on success or failure, if it is idempotent, or any authentication requirements. The agent is left with minimal understanding of side effects, making this insufficient for a mutative 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 a single concise sentence with no fluff, front-loading the core action. It is appropriately compact for a short tool, but the brevity means it omits key details. For the conciseness dimension itself, it scores well, though it could be slightly more informative without becoming verbose.

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 no output schema, sparse annotations, and an input schema lacking descriptions, the description is the only resource for an agent. It only states the high-level action and leaves critical details—such as lead structure, listing requirements, error handling, and return value—completely unexplained. This is inadequate for a tool with complex input.

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 does not. It never references the parameters 'listing_id' or 'lead', nor does it explain their structure or meaning. The 'lead' object is an arbitrary object with additionalProperties, yet the description offers no guidance on required fields or format. This is a severe gap given the flexible input.

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 verb ('Submit') and resource ('a consented consumer lead') targeted at 'a supported published listing'. It distinguishes the action from siblings by focusing on lead submission, though it does not explicitly mention alternatives. The phrase 'supported published listing' is somewhat vague, so it does not fully differentiate from related tools.

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 like 'procure' or other siblings. There are no scenarios, exclusions, or conditions that help an agent decide between this and similar tools. Usage context is implicitly the action of submitting a lead, but no explicit direction is given.

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