hostodo_upload_ticket_attachment

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

The description explicitly states that the tool does not perform the requested action, returns a structured coming_soon response, and warns against sending secrets. Given no annotations are present, this provides clear behavioral disclosure.

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 short and front-loaded with key context ('Coming soon (helpdesk)'). It efficiently conveys the stub nature and a security warning without unnecessary words.

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 stub tool, the description is sufficiently complete: it clearly communicates the non-functional state, the return type, and a security caveat. The sibling tools are more complex, but this stub's description fits its limited role.

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 the baseline is 3. The description adds no additional meaning to the parameters beyond what the schema already provides. It could have explained that parameters are used for recording intent or logging.

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 claims the tool 'Upload a ticket attachment' but then states it is a stub that does not perform the action. This creates confusion about the actual purpose, which is to record demand. It does not clearly differentiate from siblings like hostodo_create_ticket or hostodo_reply_ticket.

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 is provided on when to use this tool versus alternatives. The description does not indicate in what scenario a stub should be invoked, nor does it mention any conditions or prerequisites.

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