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

readOnlyHint=true already tells the agent this is a safe read, so the bar is lower. The description adds useful context about what fields come back (balance, monthly limit, consumption), but says nothing about permissions, error behavior, or whether consumption data is scoped to a period.

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?

One front-loaded sentence that leads with scope and then lists returned fields, followed by the REST endpoint. Tight and readable; the raw endpoint string is mildly redundant but conventional and non-obstructive.

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?

There is no output schema, so the description must and does summarize the returned fields, giving the agent enough to know what it will receive. Missing only usage context and any indication of error/missing-organisation behavior.

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 coverage is 100%: the single organisation_id parameter is documented with a UUID pattern and its provenance (obtained from smsmode_get_balance). The description adds nothing beyond the schema, so the baseline 3 is appropriate.

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 and resource ('Full details of one organisation') and enumerates the content returned: contacts, addresses, company info, balance, monthly limit, consumption. The resource is naturally distinct from siblings like get_balance or get_campaign, though the description never names an alternative to reinforce the distinction.

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 guidance, no prerequisites, and no mention of alternatives such as smsmode_get_balance for a quick balance check. The only routing hint ('from smsmode_get_balance') lives in the schema parameter description, not the tool description.

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