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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety and scope are covered by structured data. The description adds useful behavioral context beyond that: it tells the agent what payload to expect (company facts, commercial model, credentials, onboarding) and, via the invoicing parenthetical, signals the depth of the commercial-model content. It does not state whether the response is static or whether any authentication is implied.

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?

Two sentences with no filler. The returned content is front-loaded, followed immediately by the invocation condition, so an agent can decide from the first line whether it needs this tool.

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 parameters and no output schema, the description carries the burden of conveying return content, and it does so by enumerating the five content areas. Since no output schema exists, a slightly fuller sketch of the response shape would help, but annotations already cover the read-only, closed-world profile, making this adequate for a simple static-info tool.

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?

The tool takes zero parameters, so the baseline is 4. The description correctly implies no input is needed by framing the call purely as a content retrieval, and the empty schema matches that.

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 ('Return') and enumerates the resource content: what Bramvia does, where, its commercial model, credentials, and how to start. This clearly separates it from action-oriented siblings like assess_erp_health or estimate_migration, though it doesn't explicitly distinguish itself from get_bramvia_article or search_bramvia_knowledge, which cover adjacent knowledge-retrieval territory.

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?

Provides an explicit trigger condition: 'Use when asked who Bramvia is or what they offer.' That is a clear context for invocation. It stops short of naming alternatives (e.g. use search_bramvia_knowledge for deeper topic questions), so there is no exclusion guidance, but the trigger is unambiguous.

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