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

Beyond annotations, the description discloses exactly what is included and excluded from the bundle, including security-relevant behavior: dependency caches, git history, .env files, and credential files are never included. It also explains the time-limited link and portability across deployments, which are meaningful behavioral details not captured by the annotations alone.

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 three sentences, front-loaded with the core action and return value, followed by security exclusions and the import handoff. Every sentence adds useful information without repetition.

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?

An output schema exists, so the description need not explain return values in detail. It still covers inclusion/exclusion rules, security constraints, link behavior, and cross-deployment compatibility, leaving no major gap for an agent to call the tool correctly.

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 coverage is 100%, so both project_id and ttl_seconds are already documented in the input schema. The description mentions a time-limited link but does not add syntax or format details beyond the schema's default and maximum ttl behavior. Baseline 3 is appropriate when the schema carries parameter semantics.

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 and resource: it packages a project into a portable bundle and returns a time-limited download link. It also distinguishes the output from import_project by explaining the bundle's intended handoff, so an agent can identify the tool without opening schemas.

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 clearly states the downstream use case: hand the bundle to import_project on this or another Server4Agent deployment. It does not explicitly say when not to use export_project, but the import context strongly implies the intended workflow.

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