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

With no annotations, the description carries the full burden. The verb 'Inspect' suggests a read-only operation, which is transparent, but it does not mention potential side effects, permissions required, or what the returned data represents. It is minimally transparent but not misleading.

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 a single, concise sentence without redundant wording. It efficiently conveys the tool's purpose with no fluff, making it easy to parse and understand.

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?

Given the simplicity of the operation and lack of output schema, the description is mostly complete for a simple inspection. However, it could briefly mention the return format or typical use case, but the current level is acceptable for a getter with minimal parameters.

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 sole parameter 'agent_key' is not described in the schema or the description. Since schema coverage is 0%, the description must compensate, but it does not explain the meaning, format, or optionality of the parameter. The name gives a hint but is insufficient for unambiguous usage.

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 the action ('Inspect') and the specific resource ('persistent machine spending mandate'), which is a precise and unique capability among the sibling tools. It distinguishes itself from other getters by focusing on the spending mandate rather than generic status or planning data.

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 implies usage for inspecting spending mandates but does not explicitly state when to choose this tool over alternatives or provide context on typical scenarios. It is adequate for a simple read operation but lacks explicit guidance on conditions or prerequisites.

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