get_heuristic

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

No annotations are provided, so the description carries full burden for behavioral disclosure. It only says 'Sync lookup', implying a read operation but without confirming it's non-destructive or side-effect-free. There's no mention of return format, permissions, or error conditions.

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 extremely concise (one sentence with version prefix), which is good for conciseness but borders on under-specification. It could include more information without becoming lengthy.

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 annotations, no output schema, and a single parameter, the description is incomplete. It does not specify what the tool returns (e.g., the heuristic object, success status), any prerequisites, or potential errors. More context is needed for an agent to use it effectively.

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 has 0% description coverage, and the description does not add any meaning to the single 'id' parameter beyond stating it's a HeuristicId. No format, constraints, or examples are given.

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 states 'Sync lookup by HeuristicId', which clearly indicates a synchronous retrieval operation for a specific heuristic. It distinguishes from sibling tools like list_heuristics (which lists all) and add_heuristic/remove_heuristic (which modify). However, it could be more explicit, e.g., 'Retrieve a heuristic by its ID'.

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. There are many heuristic-related sibling tools (list_heuristics, match_heuristics, etc.), but the description does not help the agent decide when to choose get_heuristic over others.

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