cuemap_project_pull

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

No annotations are provided, so the description carries the full burden. It discloses key behavior: uses the engine host's AWS CLI, requires explicit approval, and never overwrites existing projects. This goes beyond the schema and gives an agent important safety-relevant context.

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?

Two compact sentences with no filler. Critical constraints are front-loaded and every clause earns its place.

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?

For a safety-sensitive install operation with no annotations and no output schema, the description is largely complete: it explains the action, source, prerequisite, and non-destructive guarantee. It does not describe response format or what happens after success, but that is a minor gap here.

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 100%, with both source and confirmed having descriptive meanings. The description reinforces the exact S3 source requirement but adds little parameter-specific detail beyond what the schema already provides.

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?

States a specific action: download, install, and warm a .cuemap package from an S3 source using AWS CLI. The resource and operation are clear, and this clearly differentiates from sibling tools like push, load, or sync.

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 a clear prerequisite: use only after explicit approval of the exact S3 source. Does not explicitly name alternatives or when-not-to-use scenarios, but the context is sufficient for an agent to gate invocation.

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