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

No annotations are provided, so the description carries the full behavioral-disclosure burden. It mentions COP and SECOP II scope, but does not state whether the tool is read-only, what permissions or data freshness constraints apply, or how the analysis is computed.

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 with no filler, so it is efficiently concise. Its brevity reflects under-specification for a five-parameter analysis tool rather than wasteful wording.

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?

An output schema exists, so return values need not be explained in the description. However, for a no-annotation analysis tool with five parameters and zero schema coverage, the description omits usage guidance and parameter semantics that an agent would need to invoke it 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% for five parameters. The description only indirectly maps to the dataset parameter by mentioning 'procesos o contratos'; it does not explain limit, keyword, modalidad, or departamento, so it 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 states a specific verb and resource: it executes a financial and contractual-concentration analysis in COP over SECOP II processes or contracts. It is clear what the tool does, but it does not explicitly distinguish itself from siblings such as secop_search_processes or secop_inspect_opportunity.

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 guidance on when to use this tool versus the sibling search or inspection tools. It implies that it performs analysis on processes or contracts, but offers no prerequisites, 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?

With no annotations, the description carries the full burden: it does convey that this is a live status check ('estado en vivo') rather than a mutation, which is valuable. However it does not say whether it performs an outbound/network probe, whether it can be slow or fail, or what side effects (if any) a call has.

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 with no filler; the core object of the diagnosis is stated immediately. It is slightly jargon-dense ('puente bidireccional', 'proyecto SCRAPPING') but not padded.

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 (0 params) and an output schema exists, so the description needn't explain return values. What is still missing is any notion of what the status result means or what a degraded bridge implies, but overall the description is sufficient 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?

The tool takes zero parameters, so there is nothing for the description to disambiguate; baseline 4 applies. No parameter guidance is needed or missing.

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?

Uses a specific verb ('Diagnostica') bound to a specific resource ('estado en vivo del puente bidireccional entre MCP-SECOP y el proyecto SCRAPPING'), so an agent can tell this is a health/diagnostics probe. It does not explicitly differentiate itself from the listed siblings, though the resource is distinct enough that confusion is unlikely.

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 diagnostic framing implies the usage context (checking connectivity between MCP-SECOP and the SCRAPPING project), but the description never states when to call it, when not to, or what alternative exists if a diagnostic fails. Usage must be inferred from the verb 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?

With no annotations the description carries the full burden. It usefully discloses the output form (Markdown chunks with institutional headers and metadata) and target systems (Qdrant/Chroma), but says nothing about whether chunks are persisted/embedded, side effects, permissions, or idempotency.

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 with zero waste. It is efficient, though the brevity contributes to under-specification given the tool's complexity.

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 9-parameter tool with no annotations and 0% schema coverage, the description is too thin. The output schema means return values needn't be explained, but the filtering semantics and operational context an agent needs to call it correctly are absent.

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?

Nine parameters with 0% schema description coverage, yet the description mentions none of them. Filters like estado, dataset, entidad, keyword, modalidad, cuantia_min, departamento, and chunk_size_chars are left entirely to bare schema names with no added meaning or default behavior.

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: 'Genera chunks semánticos en Markdown' with contextual headers and metadata for RAG stores. The purpose is clear and distinct from search/crawl/inspect siblings, though it never explicitly names an alternative to differentiate itself.

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 when/when-not guidance, no mention of prerequisites (e.g., whether source data must be ingested or the bridge healthy), and no explanation of how to choose filters versus the seven sibling tools. Usage is only implied by the name.

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 and discloses almost nothing: it does not say whether this is a pure read of static reference data, whether results are cached, or whether any side effects occur. Only the output schema hints at the return shape.

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 efficient sentence with the resource front-loaded and no filler. It is concise, though brevity costs it the parameter and usage detail it needed.

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 output schema exists, so return values need not be explained. However, the meaning of the sole optional parameter and the intended usage context are both missing, which leaves real gaps for an agent deciding whether to filter.

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 description never mentions 'category_code', so an agent cannot tell what the optional filter does or what values it accepts (no enum). With one undocumented parameter, the description fails to compensate for the schema 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 ('Devuelve') and resource ('mapa taxonómico') and even quantifies scope (6 dominios, 11 enlaces). It is clearly distinct from search/crawl siblings, though it never names those alternatives explicitly.

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 call this versus the other SECOP tools, and no mention of prerequisites or typical workflow position. The only implicit cue is that this is reference/discovery data rather than a search.

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 the full behavioral burden. It hints at the mechanism (DOM tables, __VIEWSTATE, attached documents), which suggests a live page fetch/parse that could be slow or fail on a changed page, but it says nothing about cost, auth, rate limits, failure modes, or what happens with a malformed URL. For a network-scraping tool with zero annotation coverage this is a real 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?

One compact sentence with the resource and the extracted artifacts front-loaded; nothing is wasted. It is arguably too terse for a network-fetching tool rather than padded.

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?

An output schema exists, so return values need not be described, and the description does list the extracted artifacts. What is missing for a 1-param scraping tool is operational context: prerequisites, expected URL form, and rough cost/latency expectations.

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% for the single process_url parameter, so the description must compensate. It does identify the expected input as an 'OpportunityDetail' URL, which adds meaning beyond the bare parameter name, but it gives no format details or says whether other URL shapes are accepted or rejected.

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 ('Inspecciona en profundidad') and a specific resource (an OpportunityDetail URL from SECOP II), and enumerates what it extracts (DOM tables, __VIEWSTATE, attached pliegos). This clearly reads as a deep-page scraper and is distinguishable from secop_search_processes, though the description never names a sibling to contrast with.

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 phrase 'en profundidad' implies a deep-dive usage relative to lighter tools, but there is no explicit when-to-use, when-not-to-use, or named alternative among the seven siblings. The agent must infer that this is the follow-up step after finding a notice UID.

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 and discloses almost nothing: it does not say what creating a feed actually does, whether it is idempotent or destructive, what 'sincronizado' means operationally, or which parameters are required for creation versus listing.

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 compact sentence with the verb front-loaded, so there is no padding, but the brevity comes at the cost of under-specification rather than economy.

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?

An output schema exists, so return values need not be explained, but for a zero-required-parameter, seven-parameter tool with two distinct actions and no annotations, the description is far too thin to let an agent invoke it 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?

All seven parameters have 0% schema description coverage and the description mentions none of them. The meaning of name, slug, keyword, modalidad, departamento, and chunk_size_chars, and how they differ between list and create, is entirely undocumented.

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 names two verbs (list/create) and a resource (dynamic RAG API feeds), which gives a rough sense of the tool, but 'feeds dinámicos de API RAG' is left undefined and 'sincronizados con el proyecto SCRAPPING' is opaque jargon. It does not differentiate itself from the conceptually adjacent sibling secop_generate_rag_chunks.

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 list versus when to create, no prerequisites, and no mention of alternatives among the seven sibling tools. The agent must infer the intended action from parameter defaults 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?

No annotations are provided, so the description carries the full disclosure burden and fails it: nothing about whether scraping is a fallback or always-on, how costly spider_enrich_top_n is, pagination/limits, rate limits, or auth. The mentions of SoQL and 'Puente SCRAPPING' gesture at backend behavior but remain opaque jargon rather than actionable 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?

A single front-loaded sentence with no filler or repetition. It is efficient, though its brevity reflects under-specification rather than disciplined economy.

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 13-parameter tool with zero annotation coverage, one sentence is nowhere near sufficient. Even granting that an output schema exists and return values needn't be described, the agent gets no guidance on filter interactions, the dataset switch, or what spider enrichment does.

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% across 13 parameters, and the description only implicitly touches one of them by naming the two datasets ('procesos o contratos') that map to the dataset enum. Filters such as ciudad, estado, entidad, nit_entidad, unspsc_code, cuantia_min/max and especially spider_enrich_top_n get no explanation of format (e.g. NIT without check digit) or effect.

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 a specific verb (busca) plus a concrete resource (procesos de contratación o contratos electrónicos) and the platform (SECOP II), so an agent knows the domain. It does not distinguish this from siblings like secop_spider_crawl or secop_inspect_opportunity, which plausibly also retrieve procurement records, leaving overlap unresolved.

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 statement of when to use this search versus spider_crawl or inspect_opportunity, no prerequisites, and no exclusions. The parenthetical '(SODA SoQL + Puente SCRAPPING)' hints at two retrieval paths but doesn't tell the agent which conditions trigger which.

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 behavioral burden, and it discloses almost nothing beyond 'asíncrono'. It does not say whether the crawl hits the live network, how long it may run, whether it needs credentials, or if it is rate-limited — all critical for a web-crawling 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?

A single front-loaded sentence with no filler, which is efficient. The brevity is under-specification rather than verbosity, but structurally it is clean.

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?

An output schema exists, so return values need not be explained. But for a 4-parameter tool with no annotations and 0% schema coverage, the description leaves too much unexplained — crawl behavior, network implications, and parameter meaning are all missing.

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% with 4 parameters (seed_url, max_links, category_filter, follow_internal_depth), none of which are explained in the description. 'clasificando enlaces' faintly hints at link handling and max_links, but the seed URL, depth control, and filter semantics are left undocumented in both schema and description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Does the description clearly state what the tool does and how it differs from similar tools?

States a verb ('Ejecuta') and resource ('Spider web asíncrono') scoped to SECOP II / Colombia Compra Eficiente, which gives a rough sense of the action. However, 'clasificando enlaces y __VIEWSTATE' is internal jargon that will not mean much to an agent, and nothing distinguishes this crawling tool from siblings like secop_search_processes or secop_inspect_opportunity.

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 indication of when an agent should crawl versus use the more targeted siblings secop_search_processes or secop_inspect_opportunity. No prerequisites, no exclusions, no alternatives are mentioned.

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