decode_entity_guid

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

With no annotations, the description carries full behavioral burden. It describes the decoding action and revealed components, but does not explicitly state that the tool is read-only, non-destructive, or what happens on invalid input. This is a minor gap for an otherwise safe operation.

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 concise sentences front-load the purpose, with no wasted words. Every sentence adds value. The description is appropriately sized for the tool's simplicity.

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?

The tool has one parameter and no output schema, but the description fully explains what the output contains (components list). Given the simplicity and lack of complex behavior, the description is complete for an agent to understand and invoke the tool.

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 description adds value beyond the schema: it specifies that the GUID is base64-encoded and lists the decoded components (account ID, domain, entity type, domain ID). Schema coverage is 100%, so baseline is 3, but the extra context justifies a 4.

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 tool's purpose: decoding a base64-encoded entity GUID to reveal its components. It distinguishes itself from sibling tools (e.g., entity_search, get_entity) by focusing on GUID decoding rather than querying or retrieving entities.

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 explicitly says 'Useful for understanding what an entity GUID refers to without making an API call,' indicating when to use it. However, it does not provide when-not-to-use guidance or mention prerequisites like the need for a valid GUID.

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