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 covered. The description adds nothing beyond that – no note on what the payout config contains, whether a missing config returns 404 vs empty, or any auth details.

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 in a two-sentence description. The remaining operation-ID and describe_operation pointer is front-loaded only by accident.

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, 0%-coverage schema with no output schema and no explanation of the returned payout configuration, the definition is too thin. It tells the agent the endpoint exists but not what it yields or how to shape the request.

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% for 2 parameters. The path string hints that 'id' is a lease identifier, but the description never states the lease-id format or what the free-form 'query' object accepts, leaving the agent dependent on undocumented schema fields.

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 repeats the title's path notation twice ('GET /api/leases/:id/payout-config') and adds an operation ID. It names the verb and resource but is effectively a restatement of the name/title, with no differentiation from the many sibling lease sub-resource getters (e.g. get_payment_portal_payout_configs_33088d2a9f9701efdf217a0b).

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 use this tool versus alternatives. The only actionable sentence points at describe_operation for request schemas, which is a schema-lookup hint rather than a usage condition.

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