getDataType

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

Annotations already mark as read-only. Description adds return format details: 'Returns: { status: "success", message: [{...record}] }' and mentions empty/404 when not found. This enriches behavioral understanding.

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?

Description is concise with front-loaded title, uses bullet points for key sections, and every sentence adds value. No fluff.

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 1-parameter read-only tool with no output schema, the description covers purpose, usage, return format, and error case. Complete given context.

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% with parameter description 'Data type primary key'. Description restates requirement for data_id but adds no new semantic value beyond the schema.

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 states 'Get a single data type - Fetch a single datatype record.' It clearly identifies the verb (get) and resource (data type), and distinguishes from sibling listDataTypes by specifying it fetches a single record.

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?

Explicitly says 'Use when: fetching one data type's record by ID.' and provides 'See also: listDataTypes (enumerate many).' This gives clear context for when to choose this tool over alternatives.

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