alterios_get_form

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

The word 'Read' implies a non-destructive operation, which is adequate but minimal. No annotations are provided, so the description carries full burden for behavioral disclosure; it lacks details on permissions, errors, or rate limits.

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 8 words is highly concise, but it could be slightly more informative without losing brevity. Front-loaded with the purpose.

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 the presence of an output schema, return values are covered. However, the description lacks usage guidelines and parameter semantics, making it incomplete for a tool with 3 parameters and 0% schema coverage.

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?

With 0% schema description coverage, the description adds minimal meaning beyond parameter names. It mentions 'by ID' for form_id but does not explain profile or project_id, leaving their purpose unclear.

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?

Description clearly states 'Read a full Alterios form object by ID', specifying a verb (Read) and resource (full form by ID). This distinguishes it from sibling tools like alterios_get_view (view) or alterios_list_fields (fields).

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 guidance on when to use this tool versus alternatives like alterios_get_view or alterios_list_fields. No context about prerequisites or typical use cases.

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