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

With no annotations, the description carries the full burden. It clearly indicates a read-only operation by stating 'Return metadata,' which implies no side effects. It also discloses what specific metadata will be returned. There are no apparent behavioral surprises, making the transparency adequate for a simple metadata 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?

The description is a single, concise sentence that immediately states the purpose and enumerates the metadata fields. Every word earns its place, and the structure is perfectly front-loaded with the action verb and resource.

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 trivial complexity (no parameters, no output schema), the description fully covers what the tool does and what it returns. It is complete for its intended purpose and clearly differentiates from sibling tools that access specific data domains.

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 input schema is empty with 100% coverage (trivially). The baseline for 0 parameters is 4, and the description does not need to add parameter detail since there are none. It adds no param semantics because none are required.

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's purpose: 'Return metadata about this MCP server.' It explicitly lists the metadata components (version, data source, coverage, tool list), using a specific verb ('Return') and resource ('MCP server'). This uniquely distinguishes it from sibling tools that search/get specific records.

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 when to use the tool (when server metadata is needed) but does not explicitly state usage context or mention alternatives. No exclusions are provided, but the intended use is fairly obvious. A more explicit statement like 'Use this to understand server capabilities or data coverage' would strengthen 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?

No annotations are provided, so the description carries the behavioral burden. It conveys a read-only operation ('Get') and adds context about the case number format (e.g., 'PRC/2023/1'). However, it does not disclose possible error behavior, return format, or any limitations, which is a minor gap for a lookup 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?

The description is a single, front-loaded sentence that immediately states the action and resource. It includes useful examples without superfluous words. 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?

For a simple getter with one parameter and no output schema, the description provides the essential information: what the tool does, how to specify the case number, and realistic examples. No additional context is necessary given the tool's low 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?

The schema already describes case_number as 'AdC case number' (100% coverage), but the description adds meaningful examples of the expected format ('PRC/2023/1', 'Ccent/2022/5'). This goes beyond the schema's generic description, helping the agent understand exact input syntax.

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 'Get a specific AdC decision by case number' clearly states the verb (Get), resource (AdC decision), and identifier (case number). It distinguishes itself from sibling tools like pt_comp_search_decisions (searching) and pt_comp_get_merger (mergers) by focusing on fetching a specific decision.

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 usage when the user already has a case number, and provides examples of valid formats. It does not explicitly state exclusions or name alternatives, but the context is clear for a simple getter tool. The sibling names (search_decisions) suggest when to use search instead, though this is not explicit.

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 full burden. It only states 'Get', implying a read operation, but does not disclose return format, error behavior, or any permissions. For a simple getter this is sparse, and the agent lacks behavioral context beyond the action itself.

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, front-loaded sentence that is entirely on-topic. Every word contributes to the purpose, with no fluff or repetition.

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 nested objects) and the absence of an output schema, the description is minimally adequate. However, it does not mention what the response contains or any caveats, which would be helpful for a getter without structured output metadata.

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 the parameter already described as 'AdC merger case number'. The description does not add any additional meaning beyond the schema, so it meets the baseline without enhancement.

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 gets a specific AdC merger control decision by case number. The verb 'Get' and resource 'merger control decision' are specific, and it distinguishes itself from siblings like pt_comp_get_decision and search tools by focusing on merger decisions and case numbers.

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?

Usage is implied by the phrase 'by case number' but no explicit alternatives or exclusions are mentioned. It does not say when to prefer this over pt_comp_get_decision or pt_comp_search_mergers, so guidance is minimal.

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 carries the full burden. It discloses that the list is filtered to sectors with enforcement activity and includes counts, but does not explicitly state that the operation is read-only or describe any side effects, authentication requirements, or limitations. The description adds some behavioral context but is not exhaustive.

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, front-loaded sentence that states the primary action and the essential output components (sectors, decision counts, merger counts). Every word contributes meaning, with 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 simple list tool with no parameters and no output schema, the description adequately conveys the purpose and the expected result. It could potentially mention pagination or sorting, but these are not critical for a sector list. The addition of 'with AdC enforcement activity' clarifies the filter, making it complete enough for typical use.

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, so the schema coverage is 100%. Per the rubric, 0 params yields a baseline of 4. The description adds no parameter details because there are none, which is appropriate and does not need to compensate.

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 'List' and resource 'sectors', and clearly distinguishes itself from sibling tools by focusing on sector-level aggregation with decision and merger counts. It is not a tautology and immediately conveys 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 implies usage for sector-level overview, as it lists sectors with activity and counts. However, it does not explicitly state when to use this tool over the search/get sibling tools, nor does it mention alternatives 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 the full transparency burden. It discloses the return fields (case number, parties, outcome, fine amount, Lei da Concorrencia articles) and clearly indicates a search (read) operation, but does not address pagination, rate limits, or data coverage boundaries.

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: one for purpose and one for return content. It is front-loaded, specific, and contains no 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?

The description covers the core function and return fields, which is sufficient given the schema handles parameter documentation. It could be more explicit about limitations (e.g., not covering mergers) but overall is complete for a search 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 coverage is 100%, with all five parameters described in the input schema. The description adds no additional parameter-specific meaning beyond what the schema already provides, so the baseline of 3 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 clearly states the tool performs full-text search across AdC enforcement decisions, with specific examples of decision types (abuse of dominance, cartel, sector inquiries). This distinguishes it from sibling tool pt_comp_search_mergers, which focuses on mergers.

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 usage for searching enforcement decisions but does not explicitly mention when to use this tool instead of pt_comp_search_mergers or other siblings. No exclusions or alternative tools are named.

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 carries the full burden of behavioral disclosure. It does disclose that the tool returns merger cases and names the fields included, which is a useful behavioral trait. However, it does not mention any additional behaviors such as query semantics, ordering, or potential limitations like pagination.

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 that front-loads the main action and resource, then adds relevant return information. It contains zero wasted words and is 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?

The tool is relatively simple with four parameters fully described in the schema. The description provides enough context about the tool's purpose and return value, though it does not explain how the search works or how it relates to sibling tools. Overall it is adequate for a basic search 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?

The schema description coverage is 100%, so parameters are already fully documented in structured data. The description does not add any additional meaning to the parameters beyond what the schema provides, so the baseline score of 3 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 clearly states the tool's purpose with a specific verb ('Search') and resource ('AdC merger control decisions'), and clarifies the scope ('concentracoes de empresas'). It also lists the key return fields (acquiring party, target, sector, outcome), which distinguishes it from the sibling search tool pt_comp_search_decisions.

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 clearly indicates that this tool is for searching merger control decisions, which gives a clear context for use. It does not explicitly mention when to prefer this over pt_comp_search_decisions, but the specialized focus on mergers makes the intended usage obvious.

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