list_agent_artifacts

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 only states it uses GET and requires an agent_id, but does not mention pagination, permission requirements, rate limits, or what fields are returned. For a read operation, 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?

The description is extremely concise, with no wasted words. It front-loads the purpose and includes the endpoint and parameter example. Every sentence is necessary.

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 that an output schema exists, the description does not need to detail return values. However, the description is minimal and does not note that it returns a list (though implied by 'List'), nor does it mention pagination or limits. With many sibling tools, slightly more context would help. It is adequate but not thorough.

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%, so the description must compensate. It adds 'for example bc-...' which gives a hint about the format, but does not explain where to find the agent_id or its constraints. This adds some meaning beyond the schema, but not enough for full clarity.

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 'List artifacts produced by a Cloud Agent', which is a specific verb and resource. It also provides the HTTP endpoint for additional clarity. Among siblings, this tool is distinct from 'download_agent_artifact' which downloads a specific 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?

The description gives context by showing the HTTP method and an example agent_id, but it does not explicitly state when to use this tool versus alternatives, nor does it mention any conditions or exclusions. Usage is implied but not guided.

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