get_fieldgroup

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

Only states 'Read-only', which is minimal. With no annotations, description should disclose more about authentication, error handling, rate limits, or response format, but does not.

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?

Single sentence of 13 words, front-loaded with purpose. No unnecessary words, highly concise.

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?

Given lack of output schema and annotations, and only 2 parameters, the description is too brief. Does not specify what 'full field definitions' includes, no example usage, no constraints.

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 0%, so description must add meaning. It mentions 'by its altId' which loosely maps to fieldgroup_id, but there is mismatch in naming. Does not explain access_token or provide any parameter details.

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?

Clearly states the verb 'Fetch', the resource 'full field definitions inside a specific fieldgroup', and the identifier 'by its altId'. Distinguishes from siblings like list_schema_fieldgroups which list fieldgroups, not their contents.

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 explicit guidance on when to use or when not to use. Does not mention prerequisites, alternatives, or context compared to sibling tools.

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