ora_ticket_get

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

Description discloses what will be returned (title, description, comments, labels, assignees), implying a read-only operation. However, no explicit mention of idempotency, permissions, or error conditions. Without annotations, the description carries the burden and provides moderate transparency.

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?

Single sentence in French efficiently conveys purpose and return content, with no wasted words. Perfectly concise for the tool's simplicity.

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?

Despite lacking an output schema, the description explicitly lists the return components (titre, description, commentaires, labels, assignees), providing complete context for a simple retrieval tool. No additional detail is 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%: all three parameters (repo, issue_number, project_path) have clear descriptions. The tool description adds no further parameter guidance beyond the schema, meeting the baseline.

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 retrieves full content of a GitHub Issue, listing specific components: title, description, comments, labels, assignees. It is distinct from siblings like ora_ticket_list (listing) and ora_ticket_update (updating).

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 explicit guidance on when to use this tool versus alternatives like ora_ticket_list (for summaries) or ora_ticket_update. The usage context is implied but not spelled out.

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