model_fields_get

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

No annotations exist, so the description carries the full disclosure burden. 'Accessible' hints that results are filtered by permissions, but the description says nothing about invalid-model behavior, whether an untested connection_id is accepted, or whether all fields are returned at once versus paginated.

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 front-loaded sentence with no filler, which is appropriate for the size of the tool. The terseness borders on under-specification, but no sentence is wasted.

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?

With two required parameters at 0% schema coverage, no annotations, and no output schema, the description should explain the connection_id/model relationship and the shape of what comes back. Instead it supplies one clause, leaving the agent to guess how to populate connection_id.

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 0% and the description only implies that 'model' identifies which model's fields to read. The required 'connection_id' parameter is never explained — no hint about format, where to obtain it, or its relationship to connection_list.

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 (read) and resource (field definitions of one model), which is clear and distinguishable from the sibling model_list. It stops short of naming the sibling explicitly, so differentiation is inferential rather than stated.

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?

There is no when-to-use guidance, no mention of when to prefer model_list or record_get, and no stated prerequisites (e.g., whether connection_test must pass first). Usage is only implied by the word 'accessible'.

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