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

Annotations already cover the safety profile (readOnly/non-destructive), and the description adds substantial behavioral context beyond them: anonymous access returns only official samples and otherwise yields 401, per-mode latency ('meta' saves 10+ seconds, 'detail' may take ~30 seconds), and the return envelope shape. This is exactly the auth and performance disclosure the agent needs.

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?

Front-loaded with the authentication caveat, then purpose, id source, mode tradeoffs, and output shape in clearly labeled sections. It is somewhat long and the mode section repeats schema text, but every block is navigable and 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 read-only retrieval tool with no output schema, the description covers everything needed to call it correctly: auth behavior, required id format ('d'-prefix vs the unusable 'I...' URL slug), default and alternative modes with cost implications, and the return envelope. Nothing material is missing.

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 the schema already documents id, mode, and locale. The description's mode explanations largely duplicate the enum descriptions in the schema, so it adds little beyond the baseline; a 3 is appropriate when the schema does the heavy lifting.

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 verb and resource ('Returns the ADL and attachments for one IceShore project') and names the sibling tools that supply the required id (list_projects / list_samples). An agent can distinguish this lookup tool from list_projects, list_samples, and save_content without opening any schema.

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?

Gives concrete usage contexts (referencing existing projects, verifying the result of a save/update, with get_content(mode='detail') positioned as the canonical post-save state). It routes the agent to list_projects/list_samples for the id, but stops short of explicitly stating when NOT to use it.

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