directus_get_schema_snapshot

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 fails to disclose the return format (JSON/YAML?), whether the operation is read-only (implied by 'Get' but not stated), potential size limitations, or authentication requirements.

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 concise sentence, but the '[UNIFIED]' prefix appears to be metadata noise that doesn't add value for the agent. It is appropriately brief but sacrifices necessary detail given the lack of schema annotations.

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?

With 0% schema coverage, no annotations, and no output schema, the description should explain the 'site' parameter and return structure. As written, it leaves critical gaps in the contract needed for successful invocation.

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% (the 'site' parameter is undocumented), and the description adds no information about what 'site' represents (URL, ID, name) or valid formats, leaving the parameter effectively unexplained.

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 'Get[s] complete schema snapshot' with a specific use case ('for migration/backup'). However, it does not distinguish this from sibling tools like directus_schema_diff or directus_schema_apply, which are related schema operations.

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?

While 'for migration/backup' implies a usage context, there is no explicit guidance on when to use this tool versus alternatives (e.g., when to snapshot vs. diff), nor are prerequisites or exclusions mentioned.

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