h1_get_program

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

With no annotations, the description carries the full burden for behavioral disclosure. 'Get program details' implies a read-only operation but does not disclose response format, required authentication, error behavior, or any other operational traits beyond the tool name.

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 and front-loaded, but it is under-specified. It is not redundant or verbose, yet it lacks the detail needed to be genuinely useful, so it does not fully earn its place as the sole source of 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?

The tool has one parameter, no output schema, and no annotations. The description does not specify what fields constitute 'program details', what the return structure looks like, or how this differs from related getter tools. This is insufficient for an agent to invoke the tool with full confidence.

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 input schema has one required parameter, program_handle, with 100% description coverage. However, the description 'Program handle' is tautological, and the tool description adds no additional meaning about handle format, source, or relationship to other parameters. The baseline of 3 applies because schema coverage is high, but no extra semantic value is provided.

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 program details' uses a specific verb and resource, indicating it retrieves a single program. However, 'details' is vague and does not distinguish it from sibling tools like h1_get_program_weaknesses or h1_get_program_scopes, which also fetch program-related information.

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 such as h1_list_programs or h1_get_program_scopes. The only implied usage is when program details are needed, but there are no explicit context cues or exclusions.

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