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

Annotations already declare readOnlyHint=true, so safety is covered. The description adds the useful fact that the payload is a specific settings record scoped to either a coach or a gym, but says nothing about defaults, unset values, or whether branding status is derived.

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?

A single front-loaded sentence with a compact parenthetical field list; nothing redundant. Slightly dense with comma-separated fields but still readable.

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?

Listing returned fields partially compensates for the absent output schema, which is valuable. However, the organizationId scope/default behaviour is left unexplained, so an agent cannot confidently decide what to pass.

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?

With one parameter at 0% schema description coverage, the description carries the burden, and it only hints at the organizationId mapping via 'a gym'. It never states that omitting organizationId returns the coach's own settings, which is the key decision for the caller.

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 specific verb+resource (get invoice settings) and enumerates the fields returned (legal name, address, GSTIN, tax rate, prefix, footer, branding status), scoping them to 'the coach or a gym'. This clearly separates it from update_invoice_settings, though it never names that sibling explicitly.

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 phrase 'for the coach or a gym' implies two scoping modes, but the description never says when to call this rather than update_invoice_settings or get_my_branding, and gives no exclusion or prerequisite. Usage is only inferable from the verb.

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