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

With no annotations, the description carries the full burden; it does disclose the not-yet-generated edge case ('Returns { exists: false }'), which is genuinely useful. It says nothing about permissions, whether the read is free/side-effect-free, or the shape of a populated profile.

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?

One sentence for purpose plus one short sentence for the return edge case; front-loaded, no filler, every clause earns its place.

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 low-complexity single-parameter read with no output schema, the description is nearly sufficient: it names the resource, the payload fields, and the empty-result case. Only the usage context and the populated response shape are absent.

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?

One required parameter with 0% schema description coverage, so the schema contributes nothing about agent_id. The description implies 'the agent's' profile is keyed by an agent identifier, but adds no format or provenance detail for that id.

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 and resource ('Read the agent's current signal profile') and enumerates the payload contents (ICP, offer summary, hunter weights), which clearly separates it from the sibling sdr_generate_agent_signal_profile and from generic get_agent.

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?

No statement of when to call this versus alternatives; the natural pairing with sdr_generate_agent_signal_profile (read here, generate there) is left to inference. The exists:false note hints at a check-before-generate workflow but never says it.

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