github_actions_download_workflow_run_logs

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

No annotations are provided, so the description must fully disclose behavior. However, it only states a generic action without explaining the output format (e.g., returns a redirect URL?), side effects, or authentication requirements. This is insufficient for an agent to understand the tool's behavior.

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 (4 words) but at the cost of necessary context. It is front-loaded but does not earn its place as it essentially repeats the tool name. A slightly longer description providing clarifications would be more effective.

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 minimal schema descriptions, the description fails to provide a complete picture. It omits details about the response format, error handling, or prerequisites (e.g., required permissions). The tool is simple, but the description still lacks essential context.

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?

Although schema coverage is 100% (3 parameters with descriptions), the descriptions are merely the parameter names (e.g., 'owner'). The tool description adds no meaning about how these parameters relate to the action, leaving the agent to infer context from the trivial schema descriptions.

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 'Download workflow run logs' clearly states the action and resource. While it could better differentiate from sibling tools like download_artifact or download_job_logs, the name and description together make the purpose evident.

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 on when to use this tool versus alternatives (e.g., download_job_logs_for_workflow_run, download_workflow_run_attempt_logs). The description lacks context about use cases or exclusions.

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