Get disposition

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

Annotations already declare readOnlyHint=true and openWorldHint=true. The description merely repeats 'Read-only' and adds no other behavioral information like response format, error handling, or rate limits. No value beyond annotations is provided.

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 sentence that directly states the tool's purpose and identifier options. It is front-loaded and concise, with no unnecessary words aside from the harmless read-only note.

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 simple read operation, the description adequately conveys the resource and identifiers. Given the absence of an output schema, it could mention response details, but 'Retrieve a single disposition' implies the return object, making it acceptable.

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 schema provides 100% parameter coverage with descriptions for id and idType, including enum values. The description restates that the id can be a FastBound GUID or externalId but does not add meaning beyond what the schema already explains.

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 uses specific verb 'Retrieve' and resource 'single disposition', clearly identifying the scope by FastBound GUID id or externalId. This distinguishes it from sibling search/list tools like search_dispositions and list_disposition_items.

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?

Clear context is provided: use this to get a specific disposition when you know its id or externalId. However, it does not explicitly mention alternatives or exclusions, such as using search_dispositions when the ID is unknown.

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