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

With no annotations, the description carries the load and does well: it discloses the auth prerequisite ('Requires a linked account (transport auth)'), the return shape (JSON bodies + destination paths, explicitly not repo files), cursor-based continuation from an incomplete result, and the unusual 'There is no second unsolicited reply' behavior. It stops short of describing rate limits or how large the full profile set can be.

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 primary purpose and return format, then packed with usage rules. Dense and mostly waste-free, though the run-on flow across modes and the abrupt 'There is no second unsolicited reply' fragment cost a point.

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?

No output schema exists, but the description compensates by describing what is returned (JSON bodies plus destination paths) and covers auth, the list/fetch modes, and pagination recovery. Adequate for a read tool of this shape, though it doesn't state whether a profile name must exist beforehand.

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 100%, so a 3 is the baseline, but the description adds real operational meaning: it explains the interaction between list and siteprofilename, restates the field default, and shows cursor in context ('call this with next.arguments', 'incomplete: true') that the raw 'doc:terms' example in the schema does not convey.

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 precise verb and resource ('Returns one or all of this account's named site profiles') and enumerates the content categories (privacy, terms, cookies, licence, custom_field), immediately separating it from file-based siblings by noting these come 'as JSON bodies + destination paths — not as files in a template repo'.

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 explicit selection rules for the mutually exclusive modes ('Pass list: true to see profile names, or siteprofilename to fetch one') and an explicit conditional trigger for a different workflow ('If the previous purchase_scaffold/get_scaffold result set incomplete: true, call this with next.arguments'), naming the sibling tools involved.

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