pt_comp_get_decision

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

No annotations are provided, so the description carries the behavioral burden. It conveys a read-only operation ('Get') and adds context about the case number format (e.g., 'PRC/2023/1'). However, it does not disclose possible error behavior, return format, or any limitations, which is a minor gap for a lookup tool.

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 a single, front-loaded sentence that immediately states the action and resource. It includes useful examples without superfluous words. Every part earns its place.

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 simple getter with one parameter and no output schema, the description provides the essential information: what the tool does, how to specify the case number, and realistic examples. No additional context is necessary given the tool's low complexity.

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?

The schema already describes case_number as 'AdC case number' (100% coverage), but the description adds meaningful examples of the expected format ('PRC/2023/1', 'Ccent/2022/5'). This goes beyond the schema's generic description, helping the agent understand exact input syntax.

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 'Get a specific AdC decision by case number' clearly states the verb (Get), resource (AdC decision), and identifier (case number). It distinguishes itself from sibling tools like pt_comp_search_decisions (searching) and pt_comp_get_merger (mergers) by focusing on fetching a specific decision.

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?

The description implies usage when the user already has a case number, and provides examples of valid formats. It does not explicitly state exclusions or name alternatives, but the context is clear for a simple getter tool. The sibling names (search_decisions) suggest when to use search instead, though this is not explicit.

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