wp_get_form

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

No annotations are provided, so the description carries the behavioral transparency burden. The word 'Get' implies a read operation, and the phrase 'including fields and notification actions' usefully previews the output, but the description does not explicitly state side effects, permission requirements, or behavior for invalid/nonexistent IDs.

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 one sentence, front-loaded with the verb and resource, and contains no filler. The 'including fields and notification actions' clause adds meaningful detail without unnecessary length.

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 simple one-parameter read operation with no output schema, the description provides enough information about what is returned. It could also note that this retrieves a single form and point to wp_list_forms for listing, but that is a minor gap.

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?

The single parameter 'id' is already fully described in the input schema as 'Form ID', so the description adds little beyond the schema. However, it does provide useful context by identifying the resource type as a Ninja Form.

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 ('Get') and a clearly identified resource ('Ninja Form details'), and further specifies the key content areas: fields and notification actions. This distinguishes it from list-oriented siblings like wp_list_forms and notification-updating tools like wp_update_form_notifications.

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 implies this tool is for retrieving details about a single Ninja Form, but it does not explicitly state when to use it versus alternatives. It does not mention that wp_list_forms is for listing forms or that wp_update_form_notifications is for modifying notification actions.

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