Server Quality Checklist

Tool Scores

• list_guidesC
  2.4/5.0
  Behavior2/5

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

  No annotations are provided, so the description is the sole source of behavioral disclosure. It only states the basic listing action and does not reveal pagination behavior, the effect of the 'limit' parameter, the meaning of 'poblacion_id', or the response structure. It also does not explicitly confirm the operation 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.

  Conciseness3/5

  Is the description appropriately sized, front-loaded, and free of redundancy?

  The description is a single concise sentence with no redundant text, which is positive. However, it is under-specified rather than efficiently structured, omitting critical information that an agent would need to use the tool correctly.

  Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

  Completeness2/5

  Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

  For a simple listing tool with optional parameters and no output schema, the description lacks essential context: no return format, no pagination details, no explanation of the 'poblacion_id' filter, and no distinction from other listing tools. This makes it insufficient for confident selection and invocation.

  Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

  Parameters1/5

  Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

  The input schema contains two optional parameters with no descriptions, and the tool description mentions neither 'limit' nor 'poblacion_id'. With 0% schema description coverage, the description wholly fails to compensate by explaining parameter meaning or usage.

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

  Purpose4/5

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

  The description clearly states the tool's purpose: to list published guides in Rovee, using a specific verb ('Lista') and resource ('guías'). It distinguishes from sibling listing tools by resource type, though it doesn't elaborate on what 'guides' are or how they differ from other content.

  Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

  Usage Guidelines2/5

  Does the description explain when to use this tool, when not to, or what alternatives exist?

  The description offers no guidance on when to use this tool versus alternatives like list_blog_posts or list_pois. It neither states specific use cases nor mentions any conditions where a different listing tool should be preferred.

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

• list_eventsC
  2.6/5.0
  Behavior1/5

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

  With no annotations, the description must fully disclose behavioral traits, but it only states the core listing action. It omits details about pagination, sort order, data scope, authentication, rate limits, or response format—all of which are critical for safe invocation.

  Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

  Conciseness4/5

  Is the description appropriately sized, front-loaded, and free of redundancy?

  The description is a single, front-loaded sentence that wastes no words. However, it is under-specified for a tool with parameters, so while concise, it could be better structured to include parameter semantics.

  Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

  Completeness2/5

  Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

  For a list tool with three optional filters and no output schema, the description is incomplete. It does not mention how results are returned, what the filters do, or any behavioral limitations, leaving considerable ambiguity for the agent.

  Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

  Parameters1/5

  Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

  Schema description coverage is 0%, and the description does not explain any of the three parameters (limit, categoria_id, poblacion_id). The agent has no semantic understanding of how to use these filters, making parameter usage purely speculative.

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

  Purpose5/5

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

  The description clearly states the tool's function: 'Lista los eventos programados en Rovee' (lists scheduled events in Rovee). It uses a specific verb and resource, and the 'eventos programados' scope distinguishes it from sibling tools like list_blog_posts or list_pois.

  Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

  Usage Guidelines2/5

  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. There is no mention of prerequisites, filtering scenarios, or when to prefer this over sibling list tools, leaving the agent without contextual decision support.

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

• list_businessesC
  2.8/5.0
  Behavior2/5

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

  Without annotations, the description carries the full burden of behavioral disclosure. It only states that the tool lists businesses, but does not disclose whether it is a read-only operation, how filtering parameters affect results, or any behavior about pagination or limits. No side effects or permissions are mentioned.

  Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

  Conciseness4/5

  Is the description appropriately sized, front-loaded, and free of redundancy?

  The description is a single concise sentence that gets straight to the point without wordiness. However, its brevity sacrifices valuable information; it is not inflated but rather under-specified.

  Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

  Completeness2/5

  Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

  Given the tool has three parameters and no output schema or annotations, the description is too minimal to support correct invocation. It does not explain return format, filtering behavior, or the meaning of the parameters, making it incomplete for a tool with this complexity.

  Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

  Parameters1/5

  Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

  The input schema defines three parameters (limit, categoria_id, poblacion_id) with zero description coverage. The tool description provides no explanation of what these parameters mean or how they affect the results, leaving the agent without semantic guidance.

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

  Purpose5/5

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

  The description uses the specific verb 'Lista' (lists) and identifies the resource as 'negocios registrados' (registered businesses), clearly distinguishing from sibling tools that list other content types like blog posts or POIs. This is a specific and unambiguous purpose statement.

  Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

  Usage Guidelines2/5

  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 such as list_pois or list_blog_posts, nor does it mention any prerequisites or filtering scenarios. It simply states the action without any usage context.

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

• list_poisB
  3.1/5.0
  Behavior2/5

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

  No annotations are present, so the description carries the full burden. It only states the tool lists POIs without disclosing side effects, filtering behavior, pagination, or read-only nature. This is insufficient for a no-annotation tool.

  Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

  Conciseness5/5

  Is the description appropriately sized, front-loaded, and free of redundancy?

  The description is a single clear sentence with no redundancy, front-loaded with the core purpose. It is appropriately concise for a simple list tool and easy to parse.

  Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

  Completeness2/5

  Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

  Although the tool is simple, the description lacks information about filter parameters, return format, and any usage context. With no annotations and no output schema, the description should provide more details to be considered complete.

  Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

  Parameters2/5

  Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

  Schema description coverage is 0%, and the description does not explain any of the three parameters (limit, categoria_id, poblacion_id). The Spanish parameter names hint at their meanings, but the description does not compensate for the missing schema descriptions.

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

  Purpose5/5

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

  The description uses a specific verb 'Lista' (lists) and clearly identifies the resource 'Puntos de Interés (POIs)' in Rovee. It distinguishes from sibling list tools like list_blog_posts, list_guides, list_events, and list_businesses.

  Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

  Usage Guidelines2/5

  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 publish_poi or other list tools. There are no exclusions, prerequisites, or context hints beyond the tool name and description.

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

• list_blog_postsB
  3.3/5.0
  Behavior2/5

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

  With no annotations, the description must fully disclose behavior. It states the tool lists recent posts, implying a read-only operation, but does not disclose that the default status is 'all' (including drafts) or that the default limit is 10. This omission could mislead an agent expecting only published posts, creating a transparency gap.

  Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

  Conciseness5/5

  Is the description appropriately sized, front-loaded, and free of redundancy?

  The description is a single, clear sentence in Spanish, front-loaded with the action and resource. It is concise, contains no unnecessary words, and is appropriately structured for quick comprehension.

  Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

  Completeness4/5

  Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

  The tool is a simple list operation with optional parameters, and the schema provides defaults for limit and status. The description conveys the core purpose, and the schema fills in parameter details. Although it lacks an explicit return format, 'list' implies a collection of blog posts, making it sufficiently complete for the context.

  Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

  Parameters1/5

  Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

  Schema description coverage is 0%. The description does not mention the 'limit' or 'status' parameters at all, leaving their meaning entirely to the schema. Since the description must compensate for low coverage and does not, it adds no value beyond the schema for parameter understanding.

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

  Purpose5/5

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

  The description clearly states the tool lists recent blog posts using the specific verb 'Lista' and resource 'artículos de blog'. It distinguishes from siblings like publish_blog_post (write operation) and get_blog_post (singular retrieval), making the purpose unambiguous.

  Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

  Usage Guidelines3/5

  Does the description explain when to use this tool, when not to, or what alternatives exist?

  No explicit when-to-use or alternative guidance is provided. The description implies usage because it names the resource and action, but it does not explicitly state when to use this tool versus list_pois or get_blog_post. Usage is inferred rather than directly instructed.

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

• publish_businessB
  3.4/5.0
  Behavior2/5

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

  With no annotations, the description must carry the full burden of behavioral disclosure. It only says 'creates or updates' without detailing side effects, required permissions, whether updates are partial or full replacements, or error handling. This is insufficient for a mutation tool of this complexity.

  Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

  Conciseness5/5

  Is the description appropriately sized, front-loaded, and free of redundancy?

  The description is a single, focused sentence that immediately states the tool's purpose and key fields, with no wasted words. It is appropriately sized for a CRUD tool with schema support.

  Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

  Completeness2/5

  Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

  The description provides only the basic create/update action without guidance on usage context, expected outputs, or update semantics. With 17 parameters and no annotations or output schema, the description is insufficient to fully understand the tool's behavior in context.

  Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

  Parameters3/5

  Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

  The schema covers 88% of parameters with descriptions, so the description does not need to compensate for missing parameter documentation. It merely lists a few field names that are already described in the schema, adding no new meaning. This meets the baseline but does not go beyond it.

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

  Purpose5/5

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

  The description clearly states the tool creates or updates a business/local commerce in Rovee, listing key fields like name, category, address, contact, schedule, and images. This specific verb+resource combination distinguishes it from sibling publish tools for blog posts, POIs, events, and guides.

  Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

  Usage Guidelines3/5

  Does the description explain when to use this tool, when not to, or what alternatives exist?

  The description implies usage for creating or updating businesses but does not provide explicit guidance on when to choose this tool over others like publish_poi or publish_event. It lacks any mention of alternatives, exclusions, or prerequisites, so the usage context is only implied.

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

• publish_eventB
  3.4/5.0
  Behavior2/5

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

  No annotations are provided, so the description carries the full burden of behavioral disclosure. It merely says 'Crea o actualiza' (creates/updates) without revealing side effects, required permissions, update semantics (e.g., id required), idempotency, or return format. This is a significant gap for a mutation tool with no annotation support.

  Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

  Conciseness5/5

  Is the description appropriately sized, front-loaded, and free of redundancy?

  The description is a single, concise sentence that front-loads the action ('Crea o actualiza') and lists key field categories. Every word earns its place; there is no fluff or unnecessary detail.

  Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

  Completeness2/5

  Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

  Despite having 17 parameters, the description provides only a brief overview. It does not explain create vs. update behavior (e.g., using id to update), required fields, potential validations, or what the tool returns. The rich schema covers parameters well, but behavioral context is almost entirely absent, leaving the agent under-informed for a tool of this complexity.

  Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

  Parameters3/5

  Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

  Schema description coverage is 88%, so the schema already documents most parameters. The description adds a high-level list of fields (fechas, lugar, precio, fotos, descripción, organizador) but does not provide additional semantic depth beyond what is in the schema. No parameter info is needed to compensate for low coverage, so a baseline 3 is appropriate.

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

  Purpose5/5

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

  The description clearly states the tool creates or updates an Event in Rovee, listing key fields (dates, place, price, photos, description, organizer). This is specific and distinct from sibling publish tools (publish_blog_post, publish_poi, etc.) by explicitly targeting events.

  Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

  Usage Guidelines3/5

  Does the description explain when to use this tool, when not to, or what alternatives exist?

  The description implies usage for events (create/update), but provides no explicit guidance on when to use it versus alternatives, no exclusions, and no edge cases. The tool name and scope make the primary use obvious, but the guidance is implied rather than stated.

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

• publish_poiB
  3.4/5.0
  Behavior2/5

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

  With no annotations, the description must disclose behavioral traits. It only says 'creates or updates' without explaining side effects, idempotency, whether the update requires an 'id', or any authorization needs. This is a significant gap for a mutation tool.

  Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

  Conciseness5/5

  Is the description appropriately sized, front-loaded, and free of redundancy?

  The description is a single, front-loaded sentence that conveys the core action and resource. There is zero wasted text; every word contributes to the message.

  Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

  Completeness2/5

  Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

  Given the tool has 14 parameters, no output schema, and no annotations, a one-sentence description is incomplete. It does not explain return values, error conditions, or any post-publish behavior (e.g., whether the POI becomes immediately visible). The rich schema helps but does not compensate for the lack of behavioral context.

  Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

  Parameters3/5

  Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

  Schema description coverage is 100%, so the baseline is 3. The description adds no parameter meaning beyond what the schema already provides, but the schema fully documents each parameter, including the optional 'id' for updates and coordinate examples.

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

  Purpose5/5

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

  The description clearly states the action ('Crea o actualiza' = creates or updates) and the resource ('Punto de Interés (POI)'). It distinguishes itself from sibling publishing tools (blog post, event, business, guide) by targeting POIs specifically.

  Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

  Usage Guidelines3/5

  Does the description explain when to use this tool, when not to, or what alternatives exist?

  Usage is implied by the resource name (POI), making it clear when to use this over other publish tools. However, the description does not explicitly mention when not to use it, any prerequisites, or how it relates to list_pois or upload_media.

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

• publish_blog_postA
  3.6/5.0
  Behavior3/5

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

  No annotations are provided, so the description carries the transparency burden. It discloses that the tool automatically manages translations, SEO, and taxonomies, which is useful. However, it lacks details about update semantics (how existing posts are identified), permissions, or error behavior.

  Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

  Conciseness5/5

  Is the description appropriately sized, front-loaded, and free of redundancy?

  The description is two sentences, front-loaded with the primary action and followed by a concise summary of automatic behaviors. No unnecessary words.

  Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

  Completeness2/5

  Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

  Given the tool's complexity (8 parameters, nested objects, no output schema), the description does not explain how updates are triggered (e.g., by slug or ID) or what response to expect. This is a significant gap for an agent to correctly invoke the tool for update scenarios.

  Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

  Parameters3/5

  Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

  Schema description coverage is 100%, so the baseline is 3. The description adds that translations are managed automatically, which gives context for the es/en parameters, but does not elaborate on any specific parameter beyond the schema.

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

  Purpose5/5

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

  The description clearly states the tool publishes or updates bilingual blog posts on Rovee, with a specific verb (publish/update) and resource (blog article). It distinguishes from sibling tools by mentioning automatic translation, SEO, and taxonomy management, which is unique to blog posts.

  Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

  Usage Guidelines3/5

  Does the description explain when to use this tool, when not to, or what alternatives exist?

  The description does not explicitly state when to use this tool versus alternatives like publish_poi or publish_guide, but the name and context make it clear it's for blog posts. The mention of automatic translations implies usage for bilingual content, but no exclusions or alternative references are provided.

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

• get_blog_postA
  3.7/5.0
  Behavior3/5

  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 states that the tool reads 'complete details' but does not describe return format, error handling, authentication, or special behaviors. For a simple read operation this is adequate but lacks depth.

  Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

  Conciseness5/5

  Is the description appropriately sized, front-loaded, and free of redundancy?

  One short sentence with no filler, front-loaded with the main verb and object. Efficient and to the point, with every word earning its place.

  Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

  Completeness3/5

  Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

  The tool is simple, but the description does not place it among siblings or specify return values. Since there is no output schema, the description could have clarified that it returns full post details and when to prefer this over list_blog_posts. Missing guidance on use cases makes it moderately complete.

  Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

  Parameters3/5

  Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

  The schema provides two string parameters with no descriptions (0% coverage). The description adds meaning by explaining they can be used interchangeably ('ID o slug') as lookup identifiers, which the schema does not convey. However, it does not clarify requiredness, format, or priority.

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

  Purpose5/5

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

  The description uses the specific verb 'Obtiene' (gets) targeting 'detalles completos de un artículo de blog' and specifies lookup by ID or slug. This clearly distinguishes it from sibling tools like list_blog_posts and publish_blog_post.

  Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

  Usage Guidelines3/5

  Does the description explain when to use this tool, when not to, or what alternatives exist?

  The description implies the tool is for fetching a single blog post but does not explicitly state when to use it over list_blog_posts or publish_blog_post. No alternatives or exclusions are mentioned, leaving the usage context implicit.

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

• publish_guideA
  3.7/5.0
  Behavior2/5

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

  No annotations are provided, so the description must carry the behavioral transparency burden. It states create/update but does not disclose update semantics (partial vs full), required permissions, or return values. This is minimal disclosure for a mutating tool.

  Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

  Conciseness5/5

  Is the description appropriately sized, front-loaded, and free of redundancy?

  A single, complete sentence that is front-loaded with the action and resource, with no redundant text or fluff.

  Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

  Completeness3/5

  Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

  The tool has 11 parameters and no output schema. The schema covers most parameters, but the description lacks guidance on when to use this vs sibling publish tools and does not explain update behavior. It provides a high-level purpose but misses behavioral and usage context that would make it complete.

  Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

  Parameters4/5

  Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

  Schema coverage is high (91%), yielding a baseline of 3. The description adds meaning by contextualizing the id parameter via 'Crea o actualiza' and explaining the related entity arrays via 'relacionando', which helps interpret those parameters.

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

  Purpose5/5

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

  Description clearly states it creates or updates a guide and links POIs, Events, and Businesses. The verb 'Crea o actualiza' is specific, the resource 'Guía turística o temática' distinguishes it from sibling tools like publish_poi, publish_event, and publish_business.

  Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

  Usage Guidelines3/5

  Does the description explain when to use this tool, when not to, or what alternatives exist?

  The description implies its use for guide-level aggregation but does not explicitly state when to use it vs alternatives or provide exclusions. No when-not guidance is given, so usage is inferred rather than explicit.

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

• upload_mediaA
  4/5.0
  Behavior3/5

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

  With no annotations, the description discloses core behavior: accepted input sources (local path, base64, remote URL), destination bucket, and the return of a public CDN URL. However, it omits important details like file type restrictions, size limits, overwrite behavior, or auth requirements, which are left unspecified.

  Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

  Conciseness5/5

  Is the description appropriately sized, front-loaded, and free of redundancy?

  Two concise sentences, front-loaded with the action and resource. Every phrase adds value and there is no redundancy or filler.

  Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

  Completeness4/5

  Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

  For a simple upload tool, the description covers input formats and the output URL. It lacks details on error handling, file size limits, or content type restrictions, but these may be considered secondary for an upload tool with a clear schema.

  Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

  Parameters3/5

  Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

  Schema coverage is 100% with each parameter described in the schema. The description doesn't add significant parameter semantics 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.

  Purpose5/5

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

  The description clearly states the tool uploads an image to a specific Supabase Storage bucket and returns a public CDN URL. It distinguishes itself from sibling tools, which focus on publishing content (posts, POIs, events, etc.) rather than media upload.

  Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

  Usage Guidelines4/5

  Does the description explain when to use this tool, when not to, or what alternatives exist?

  It explains the tool is for uploading images and mentions the URL can be used in posts, POIs, events, guides, or businesses. It doesn't explicitly state when not to use it or mention alternatives, but the context is clear: use this before publishing content that requires media.

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