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 value by disclosing the exact HTTP surface (GET /organization) and the full set of sensitive company configuration returned. It does not discuss auth scope beyond the token implication or rate limits, keeping it short of a 5.

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?

Three tight sentences: identity/resource first, the return payload next, then the routing hint and endpoint. No sentence is redundant, and the field list earns its length because there is no output schema.

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, the description carries the burden of documenting the return payload, and it does so field by field. Combined with the readOnly annotation, an agent has everything needed to call this and consume the result.

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?

Zero parameters and an empty schema, so there is nothing for the description to disambiguate; baseline for a param-less tool is 4.

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 (the Billy company / organization the token belongs to) and enumerates the exact fields returned (id, name, address, CVR, base currency, VAT settings, fiscal year, payment terms, invoice numbering, default accounts). No sibling tool returns organization data, so the agent can immediately distinguish it from the contact/invoice/product tools.

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?

"Good first call" gives a clear usage context: call this to bootstrap company context before other operations. It does not name alternatives or exclusions, but none of the siblings are substitutes for this resource, so the guidance is adequate without them.

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