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

With no annotations, the description carries the full burden. The statement 'Served verbatim from the site's canonical copy' adds useful context about the static, verbatim nature of the output, but it does not disclose other behavioral traits such as authentication needs or side effects, though the read-only nature 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?

The description is compact at two sentences and front-loads the main subject. The first sentence is slightly convoluted due to the 'ledger' clause, but overall it is efficient with no unnecessary redundancy.

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 simple content-retrieval tool with no parameters and no output schema, the description adequately conveys what content to expect and that it is served verbatim from a canonical source. It does not elaborate on the 'ledger' term, but this is a minor gap given the tool's simplicity.

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?

There are no parameters, so the empty schema is fully self-explanatory. As the baseline for zero parameters is 4, the description does not need to add anything further.

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 identifies the resource as 'the current offer, which is the design partnership' and clarifies its scope, distinguishing it from siblings like get_faq and get_company_overview. However, it lacks an explicit verb (relying on the tool name 'get') and includes the ambiguous phrase 'what the ledger proves'.

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 description gives no explicit guidance on when to use this tool versus alternatives. It mentions 'how to apply' but does not contrast with submit_design_partner_application, and there is no exclusions or prerequisite context.

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