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

Beyond the readOnlyHint annotation, the description discloses what the call returns: all attachments with IDs and keys, the prerendered vs client-only distinction, and an SEO warning when Data is fetched by browser fetch() only. It also communicates the behavioral rule that this is the authoritative source for attachments.

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 tight and front-loaded: it opens with the usage trigger, lists the valuable return contents in one compact sentence, and closes with a one-line caution. No sentence is wasted.

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 one-parameter read-only tool with no output schema, the description provides enough about the response content and a key warning, so an agent knows exactly what to expect and why to call it. It also sets the broader editing workflow context, making the tool's role clear.

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?

The only parameter, projectId, is already fully described in the schema as 'The project ID to retrieve' (100% coverage). The tool description adds no extra parameter semantics beyond the context that the project is a site being edited, so the schema carries the load and the baseline of 3 applies.

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 names a specific action and object: calling this first gets 'the inventory of everything attached' to a site — forms, Data collections, booking pages, chatbot — with IDs and keys. This clearly differentiates it from siblings like get_project_files or get_form by focusing on the aggregate attachment inventory rather than a single resource.

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?

It explicitly gives the trigger: 'EDITING A SITE? Call this FIRST', and warns not to infer attachments from HTML or the live URL. It doesn't name specific alternative tools for when NOT to use this one, but the directive is clear enough for an agent to decide when to invoke it.

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