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

No annotations are provided, so the description must disclose behavioral context. It implies a read operation but does not state whether it is read-only, what it returns, whether it has side effects, or why reading it is required before repeating funding provider info. The phrase 'Read this' hints at a prerequisite but leaves the actual behavior and output opaque.

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 very short and each sentence earns its place: one identifies the resource and one gives a usage directive. It is front-loaded and avoids verbiage, though the first sentence is a noun fragment rather than a clear declarative statement.

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 0-parameter tool with no output schema and no annotations, the description still leaves major gaps: what is 'referral posture', what does the returned data look like, and why must it be read before repeating list_funding_providers? The description gives a context cue but not enough for an agent to fully understand the tool's role or 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?

The tool has zero parameters and schema description coverage is 100%, so there is nothing for the description to add about parameter meanings. A zero-parameter tool gets a baseline of 4, and the description appropriately does not attempt to describe parameters.

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 tool as 'ZeroAcquire's referral posture', which is a specific noun phrase, but does not define what a referral posture is or what action the tool performs beyond the name 'get_posture'. It clearly points to a resource but lacks a concrete verb+resource statement, and it only weakly distinguishes itself from siblings via the word 'posture'.

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 explicit guidance: 'Read this before repeating anything from list_funding_providers.' This tells the agent when to invoke this tool and references a specific sibling as the alternative to consult after reading. However, it does not explain when to use get_posture in other contexts or when not to use it.

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