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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is fully covered elsewhere. The description adds nothing beyond the URL—no pagination behavior, no return shape, no scoping or auth notes—so it contributes no behavioral context of its own.

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 one substantive sentence is duplicated verbatim, wasting a third of the text, and the remainder is an operation ID and a redirect to another tool. Short, but not front-loaded with meaning.

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 nested-object tool with an opaque query bag and no output schema, the description should explain what the query supports and what comes back. It instead defers to describe_operation, leaving the agent unable to construct a correct call without a second round trip.

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% and the description explains neither the required locationId nor the free-form 'query' object, which has additionalProperties with no documented keys. Only the path template hints that locationId belongs in params, leaving the query parameter entirely 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 is a raw HTTP path repeated verbatim with no plain-language statement of intent. The path segment '/locations/:locationId/folders' does imply retrieving folders for a given location, so an agent can infer the resource, but the 'GET' verb plus URL is machine-style rather than a described action.

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?

There is no guidance on when to call this versus siblings such as get_sitefolio_locations or get_document_folders. The only actionable pointer is 'describe_operation provides native request schemas', which tells the agent to look elsewhere for details rather than when to use this tool.

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