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

Annotations already declare readOnlyHint/idempotentHint/non-destructive, so the safety profile is covered, but the description adds nothing beyond that. For an authorize endpoint the agent needs to know whether it returns a redirect/consent URL, whether it creates server-side state, or what errors occur if Xero isn't configured — none of which is disclosed.

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, wasting the only substantive line of the description. Length is short but the content is filler rather than front-loaded information.

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 no behavioral explanation beyond annotations, an agent has essentially no basis for calling this correctly — it cannot tell what the free-form query accepts or what the call returns.

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?

Two parameters (`query` and `params`) have 0% schema description coverage, and the description provides no parameter information at all. The free-form `query` object in particular is left entirely unexplained, so there is nothing to compensate for the coverage gap.

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 path and title verbatim ('GET /api/accounting-integration/xero/authorize'), which is a tautology of the name/title. It never explains what an 'authorize' call actually does (e.g. start a Xero OAuth flow, return a consent URL), and it does not distinguish this tool from the many sibling `get_accounting_integration_*` endpoints.

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?

No when-to-use or when-not-to-use guidance is given. The only actionable sentence points the agent at `describe_operation` for native request schemas, which is a discovery hint rather than usage criteria; the agent must still guess whether this starts an OAuth handshake or returns existing authorization state.

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