Get Agent Delegation

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 two real behavioral facts: metadata-only by default, and that payload retrieval involves local decryption. It omits permission/auth requirements, error modes, and what the returned metadata contains, so it is only partially transparent for a zero-annotation tool.

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 tight sentences, front-loaded with the operation and then the payload nuance. No filler, no repetition, and the most decision-relevant clause comes first.

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?

There is no output schema and no annotations, so the description should ideally say more about the returned metadata shape. It adequately covers the default-vs-payload switch and the security-relevant decryption step, but leaves auth requirements and return contents unspecified.

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?

Schema coverage is 100%, so both parameters are already documented in the schema and the baseline is 3. The description adds one genuine nuance beyond the schema by tying includePayload=true to local decryption, but the remainder restates the schema's default-vs-payload distinction.

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 ("Get one local agent delegation"), and the singular "one" implicitly separates it from the sibling agent_list_delegations. It does not name any sibling or alternative explicitly, so an agent must infer the single-vs-list routing itself.

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 explains the default behavior and how to escalate with includePayload=true, which is useful invocation guidance. It gives no when-to-use framing against agent_list_delegations or the prepare/complete/delete delegation siblings, and states no prerequisites.

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