Get VULK Project Files

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

Annotations already indicate read-only, non-destructive, idempotent, and open-world behavior. The description adds that content is omitted by default and redacted/size-limited when included, which is useful but not extensive. It does not disclose what 'redacted' entails or the return format for the manifest.

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 two sentences that front-load the main purpose and key behavioral switch. No word is wasted, and it efficiently conveys the essential information.

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?

Despite no output schema, the description is largely complete for a manifest retrieval tool. It covers the core purpose and the content inclusion option. However, it lacks details on what the manifest contains (e.g., file paths, metadata) and does not address error cases or limits on file count, which could affect agent decision-making.

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% with clear parameter descriptions. The description does not add new semantic insight beyond summarizing default behavior already captured in the schema. It meets the baseline for a well-documented 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 clearly states the tool returns a project's file manifest and distinguishes between default behavior (manifest only) and optional content inclusion with redaction and size limits. The verb 'Return' and resource 'project's file manifest' are specific, and the description differentiates it from siblings like 'list' or 'files' by specifying project-scoped file retrieval.

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 provides no guidance on when to use this tool versus alternatives. It does not mention prerequisites, edge cases, or situations where a different tool (e.g., 'files' or 'get') would be more appropriate. An explicit usage context is missing.

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