Datos completos de un Brand Book: estrategia, identidad visual (paleta + tipografía), identidad verbal (tono, vocabulario, copies). Para que un agente IA use la identidad de marca como contexto.
| Name | Required | Description | Default |
|---|---|---|---|
| section | No | Sección a consultar | all |
| brand_book_id | Yes | ID del brand book |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description must carry the behavioral disclosure burden. While the name and description imply a read-only retrieval, it does not explicitly state read-only behavior, auth requirements, error handling, or output format. 'Datos completos' is vague about actual response structure. This is a significant gap for a 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.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single, front-loaded sentence that conveys the core purpose and content. No wasted words; it is concise and directly informative.
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 viewer tool with 2 params and no output schema, the description covers the central content and use case but lacks details on return format, auth, or edge cases. The enum parameter descriptions help, but an agent might not know what to expect in the response body without additional info.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100%, so baseline is 3. The description adds meaning by detailing what each section includes (e.g., visual includes paleta + tipografía, verbal includes tono, vocabulario, copies), which clarifies the 'section' enum values. This goes beyond the schema's terse 'Sección a consultar.'
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 provides complete Brand Book data (strategy, visual identity, verbal identity), which is a specific resource with a clear scope. It uses an implied verb 'view' consistent with the tool name, but does not explicitly differentiate from sibling tools like brand_audit or visual_catalog.
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 a clear context for use: 'Para que un agente IA use la identidad de marca como contexto.' This tells an agent when to invoke it (when brand identity is needed as context). However, it does not mention exclusions or alternative tools, so it lacks explicit when-not guidance.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Each tool targets a distinct stage of the branding workflow: audit, status, viewing details, proposal, purchase, and catalog. The only potential overlap is between brand_book_status and brand_book_viewer, but their descriptions clearly distinguish progress tracking from full content access.
Tools use snake_case throughout with a mostly predictable pattern, but there is a mix of noun_noun (brand_audit, brand_book_status) and verb_noun (generate_proposal, purchase_brand_book) forms. The style is consistent and readable, though not uniformly verb-first.
Six tools is well-scoped for a niche branding service, covering discovery, sales, and delivery without redundancy or bloat. Each tool earns its place in the workflow.
The core journey from audit to proposal to purchase to accessing the brand book is fully covered, with the visual catalog as a useful resource. Minor gaps like a list-all-brand-books tool or an update tool exist, but they are likely handled outside the agent's scope.