Call any Tickiti v1 endpoint

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

No annotations are provided, and the description lacks details on whether the tool is read-only or mutating, authentication requirements, rate limits, or side effects. It only mentions that payload becomes the JSON body and path params.

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?

Two sentences efficiently convey purpose and usage instructions without redundancy. Front-loaded with key purpose, then clear actionable guidance.

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?

Given no output schema, the description should explain return format or error handling, which it does not. It also lacks mention of authentication prerequisites or expected behaviors for common endpoints.

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 covers all parameters (family, action, payload). Description adds value by explaining that family is one of the listed strings, action comes from list_endpoints, and payload includes path-param values, going beyond the schema's descriptions.

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?

Description clearly states it is an advanced escape hatch for invoking Tickiti v1 endpoints not covered by dedicated tools, and specifies that it uses family and action from list_endpoints. This distinguishes it from sibling tools like create_ticket or list_endpoints.

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?

Description instructs to use list_endpoints first to find the family and action, providing clear guidance on preparation. However, it does not explicitly state when not to use it (e.g., prefer dedicated tools).

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