Send Gestoria Message

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

Annotations already indicate mutation (readOnlyHint=false) and non-destructive (destructiveHint=false). Description adds that the message appears in a threaded context visible to both parties. Does not disclose potential errors, permissions, or notification behaviors.

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?

Bilingual description is front-loaded with English then Spanish. Appropriate length for clarity. Could be slightly more concise by merging repeated parts, but overall efficient for bilingual users.

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?

Explains threading concept, parent types, and typical use cases. Output schema exists so return format is handled elsewhere. Missing mention that the parent entity must already exist, but otherwise complete for a message sending 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?

Input schema covers all 4 parameters with descriptions. Description adds a concrete example with values, enhancing understanding. However, schema already provides clear parameter meaning, so description is supplementary rather than essential.

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?

Clearly states the tool sends a message in a contextual thread between gestor and client, with specific parent types. Distinguishes from sibling tools like gestoria_messages_list (list) and gestoria_template_bulk_send (bulk). Includes example usage.

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?

Provides specific use cases: chasing missing documents, replying to client questions, annotating presentations. Does not explicitly state when not to use or alternatives, but the context implies it's for ad-hoc individual messages as opposed to bulk or template-based sending.

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