Get Model

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is fully covered elsewhere and this description adds nothing on top. It says nothing about lookup failure behavior (e.g., unknown modelId) or what the returned detail set contains, which is the space left open by the annotations.

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?

A single short sentence with the resource and lookup key front-loaded; nothing is padded. It is efficient, though bordering on under-specification given the tool's 22-parameter schema.

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?

No output schema exists, so the description is the only place to explain what 'details' are returned, and it does not. Worse, it never reconciles the 'get one model by ID' framing with a schema containing ~20 filter, facet, and pagination parameters, leaving the agent unsure how those interact with modelId.

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 description coverage is 100%, so every parameter including the required modelId is already documented in the schema, and the baseline of 3 applies. The description's phrase 'by its ID' loosely maps to modelId but explains none of the ~20 filter/sort parameters, which is acceptable only because the schema covers them.

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 (get), resource (model details) and the identifier (ID), so the agent knows it is a single-record fetch rather than a mutation. However, it does not differentiate from near-identical siblings such as transkribus_model_get_details or transkribus_model_get_by_type, leaving the agent to guess which 'get' to call.

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?

No when-to-use guidance, no prerequisites, and no mention of alternatives like model_get_details, model_get_by_type, or model_list. The agent gets no signal for choosing this tool over its almost identically named siblings.

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