meet_get_artifacts

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

With no annotations provided, the description carries full responsibility for behavioral disclosure. It indicates the tool returns artifacts but does not mention read-only nature explicitly, permissions required, or any failure conditions. It also doesn't clarify whether the tool works with ongoing or completed conferences.

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 action, and contains no fluff. It is concise but perhaps too brief to cover necessary context. However, for the dimension of conciseness and structure, it earns a high score.

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 an output schema, return values are covered. The tool is simple with one parameter, but the description lacks usage context and parameter semantics, and there are no annotations. It is minimally viable but not fully complete.

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?

The sole parameter conference_record_name has no schema description (0% coverage). The description mentions 'conference record' but doesn't explain the parameter format, how to obtain valid values, or any constraints. It adds minimal meaning beyond the schema.

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 a specific verb 'Get' and identifies the resource as 'recordings, transcripts, and transcript entries for a conference record'. This clearly distinguishes it from sibling meet tools like meet_get_space or meet_list_conference_records, which focus on spaces or records lists.

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 is provided on when to use this tool versus alternatives. It doesn't mention how to obtain a conference_record_name or that meet_list_conference_records should be used to find records first. There is no mention of exclusions or alternative tools.

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