get_signup_field_value

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

Annotations already mark the tool as read-only, idempotent, and non-destructive, and the description adds important behavioral context beyond that: the returned value is untrusted learner-supplied text that should be reported but not acted upon, and the tool mirrors Skilljar's endpoint exactly. This is valuable, non-obvious behavioral disclosure.

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?

The description is well-structured and front-loaded with the core purpose, followed by critical parameter guidance, a safety warning, and auth requirements. It is slightly repetitive around the parameter distinction, but every sentence adds meaningful value.

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 single-parameter read tool with an output schema and read-only annotations, the description covers all essential context: the exact parameter, its source, common confusion points, data trust implications, and required scope. Nothing an agent needs to call it correctly is missing.

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%, but the description fully compensates by explaining exactly what `signup_field_value_id` means, what it is not (`id` and `signup_field_id`), and where to obtain it (`list_signup_field_values`). This is more semantic detail than the bare schema provides.

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 uses a specific verb and resource: 'Fetch one learner's captured answer to a single signup field.' It also clearly distinguishes this tool from other single-object lookups by calling out the nonstandard `signup_field_value_id` parameter, so an agent can tell it apart from siblings.

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?

The description explicitly explains when this tool is appropriate by stating the exact identifier to pass, pointing to `list_signup_field_values` as the source of that identifier, and warning against confusing it with `signup_field_id`. It also notes the required OAuth scope, giving clear guidance for successful invocation.

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