rosh_get_program

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

No annotations provided, so description carries full burden. Only discloses authentication requirement (API key). Does not mention read-only nature, rate limits, or response details. Minimal behavioral context beyond the auth prerequisite.

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 concise sentences plus an Args section. No redundant information. Front-loaded with purpose and auth requirement. Efficient use of text.

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?

Has output schema, so return values need not be explained. Description covers purpose, auth, and parameter meaning. Lacks detail on what 'details' include but is adequate for a simple get-by-ID tool.

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 coverage is 0%, but description adds 'The numeric program ID' for the single parameter, confirming type. However, schema already defines it as integer, so added value is marginal. Baseline 3 due to low coverage but simple parameter.

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 'Get details of a specific program by ID', specifying verb (Get), resource (program details), and identifier (by ID). This distinguishes it from siblings like rosh_list_programs and rosh_delete_program.

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?

Mentions 'Requires API key' as a prerequisite but provides no guidance on when to use this tool versus alternatives like rosh_list_programs or rosh_show_program. Context is clear but lacks exclusions or alternative suggestions.

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