rosh_hide_program

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

No annotations are provided, so the description must disclose behavioral traits. It states the action (hide) and auth requirement but does not indicate whether the action is reversible, if it affects existing viewers, or any side effects. For a moderation tool, this is insufficient.

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 short sentences, front-loaded with the core purpose. Every part adds value: the action, the resource, the context, the auth requirement, and the parameter explanation. No wasted words.

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 moderation tool, the description covers the essential aspects: purpose, auth, and parameter. However, it omits details about output or whether the action is reversible. Given the output schema exists, the lack of output description is acceptable, but behavioral completeness could be higher.

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%, so the description must add meaning. It explicitly explains the parameter 'identifier' as 'Program ID (numeric) or slug (string)', providing format and purpose beyond the schema's type definition.

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 uses the specific verb 'Hide' and resource 'program' with context 'from public view (moderation)', clearly distinguishing it from siblings like rosh_show_program, rosh_delete_program, and rosh_publish.

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 mentions 'Requires API key with moderate scope' but provides no guidance on when to use this tool versus alternatives (e.g., rosh_delete_program) or when not to use it. No usage context or exclusions are given.

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