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

Annotations already declare readOnlyHint and idempotentHint, so safety is known; the description adds real depth beyond that — an access restriction ('Internal Coderbuds staff only'), a warning that rules drift and must be re-read rather than trusted from old documents, and semantics for the returned groups (retired = abandoned wedges, evidence:null = ungrounded, proposed = non-binding). It doesn't specify output shape beyond the seven groups, but for a no-param read tool that is a minor gap.

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?

Front-loaded with access scope and purpose, then the primary usage directive, then a bulleted reading guide for the three tricky fields. It is on the longer side and carries a bit of narrative color about past outbound mistakes, but nearly every line maps to a decision the agent must make when calling.

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 return-value burden and does so: it enumerates the seven returned groups and explains the meaning of retired, evidence:null, and proposed. Combined with the access restriction and the before-writing directive, an agent has everything needed to call it correctly.

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 no parameters (0 params, empty schema), so there is no parameter semantics to describe and the baseline is 4. Nothing in the description is needed to compensate for a schema gap.

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 resource (the ICP / 'who it is for' rules behind /admin/prospects) and what it governs ('what an opener is allowed to say'), with a clear verb of retrieval ('as they stand today'). It also differentiates itself from siblings by naming get-prospect-worklist and propose-icp-rule, so an agent can place it without opening the schema.

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?

Explicit guidance: 'Call this before writing anything to a prospect, alongside get-prospect-worklist', clarifying the worklist says who to write to while this says what the message must be. It names the alternative for the complementary case ('Use propose-icp-rule when outbound teaches you something this list does not say'), so both when-to-use and when-not are covered.

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