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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered. The description adds nothing beyond that — no note on what config is returned, whether it is workspace-scoped, or any auth/permission nuance.

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 first sentence is duplicated verbatim, which is pure waste, and the operation ID is a machine artifact rather than useful prose. Structure is nominally front-loaded but the content is filler.

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 no output schema, no parameter documentation, and a fully opaque endpoint, the description should carry the burden of explaining what this config returns and how to shape the request. It does not, leaving an agent dependent on a separate describe_operation call.

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 both parameters (query, params) are undocumented pass-through objects with nested additionalProperties. The description gives no parameter semantics at all; delegating to describe_operation is a pointer, not an explanation of what goes in query or params.

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 only restates the HTTP method and path ('GET /api/sitefolio/config') that are already encoded in the tool name and title. It never says what the config actually contains or why an agent would want it, so it is essentially a tautology of the identifier.

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?

The only actionable hint is that 'describe_operation provides native request schemas', which points at a discovery tool but does not say when to call this versus siblings like get_sitefolio_locations or get_sitefolio_sync_history. No when/when-not guidance or preconditions are given.

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