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

Annotations already mark the tool as read-only, idempotent, and non-destructive, so the description adds value by specifying zero-input behavior, public evidence, and the limitation that it does not state consulting or advisory availability. No contradictions with annotations.

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 short sentences deliver the primary function and a key limitation with no filler. The main action is front-loaded in the first sentence.

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 an empty input schema, strong annotations, and an output schema present, the tool is simple to invoke correctly. The description gives enough purpose and boundary context, though a bit more detail on how this differs from assess_dan_role_fit or get_site_guide would improve completeness.

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 schema has no parameters and full coverage, so there is little to explain; the description reinforces this with 'zero-input.' This meets the baseline for a zero-parameter tool.

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 clearly states that the tool returns a public evidence bundle for engagement-fit clients, using a specific verb and resource. The name and title further distinguish it from assess_dan_role_fit, though the description itself does not explicitly contrast with that sibling.

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?

It provides a clear audience and context: established engagement-fit clients using their own local context. The negative statement about consulting or advisory availability signals a boundary, but it does not name alternative tools such as get_services or get_contact_options.

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