get_ticket_form

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

Annotations already declare readOnlyHint, openWorldHint, and idempotentHint, covering safety and idempotency. The description adds the return context (ordered list of ticket_field_ids) but does not elaborate on other behavioral traits such as auth requirements or rate limits. Given annotation coverage, a score of 3 is appropriate.

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, minimal waste. First sentence delivers action and primary output clearly; second sentence provides alternative usage guidance. No redundant or vague language.

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?

The tool is simple (fetch by ID) with full schema coverage, but no output schema exists. The description adequately explains what is returned (ordered ticket_field_ids) and provides usage context. No major gaps, though it could be more explicit about the structure of the return if needed.

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 description coverage is 100%, so the schema already documents both parameters. The description adds no additional meaning to parameters; it focuses on output and usage. Baseline 3 is correct.

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 'Fetch one ticket form by ID with the full ordered list of `ticket_field_ids`', specifying the verb, resource, and unique output. It distinguishes from sibling 'find_form_usage' by stating a different use case.

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?

Explicitly says when to use ('Fetch one ticket form by ID') and when to prefer an alternative ('For impact analysis before retirement, prefer `find_form_usage`'), providing clear context-sensitive guidance.

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