open-context

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

Discloses caching behavior ('cache information') and return content ('action metadata, inputs, and outputs'), which adds value since no annotations are provided. However, lacks details on error handling, rate limiting, or authentication requirements for the GitHub API.

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?

Single sentence that is well-structured and front-loaded ('Fetch and cache'). No redundant words; efficiently conveys the tool's function without unnecessary elaboration.

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?

Reasonably complete for a simple 2-parameter fetch tool, mentioning the caching aspect and return structure. However, given the lack of annotations and output schema, it should ideally disclose authentication needs or error behavior for GitHub API calls.

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 100%, so the schema fully documents both parameters. The description adds no parameter-specific details, but this meets the baseline expectation when structured documentation is complete.

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?

Clearly states the tool fetches and caches GitHub Action metadata from the GitHub API. However, it does not explicitly distinguish when to use this versus sibling 'get' tools like get_docker_image or get_terraform_info, though the domain specificity (GitHub Actions) provides implicit differentiation.

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?

Provides no guidance on when to use this tool versus alternatives, prerequisites like authentication, or conditions where it might fail (e.g., private repositories requiring tokens).

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