static_web_get_artifact

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

No annotations are provided, so the description must carry full behavioral weight. It only states 'Read a local artifact' but does not disclose error behavior (e.g., missing artifact), idempotency, or whether it requires a specific session state. For a read-only tool, it lacks clarity on what happens in edge cases.

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 a single sentence, front-loaded with the key action. It wastes no words. However, it under-specifies important details, which slightly reduces the score from maximum.

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 the tool has only 2 parameters and an output schema exists, the description is incomplete. It does not explain what constitutes an 'artifact', how to obtain an artifact_id, or the relationship to the output. The agent cannot confidently use this tool without guessing.

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 description coverage is 0%, yet the description adds no meaning to the parameters 'name' or 'artifact_id'. The default 'content.md' for name hints at a filename, but no explanation is given. The agent has no guidance on how to supply these values.

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 clearly states it reads a local artifact created by a specific action. The verb 'Read' and resource 'local artifact' are explicit. It distinguishes from siblings like action_web_click or static_web_extract by focusing on retrieval of a previously created artifact.

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., static_web_extract). It does not mention prerequisites or conditions for use. The agent has no context to decide between reading an artifact and extracting content.

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