get_party

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

Annotations already indicate readOnlyHint=true and destructiveHint=false, so the safe-read profile is known. The description adds valuable behavioral specifics: it enumerates the fields returned and explains that embed='tags,fields' includes those in a single round-trip. It does not cover not-found behavior or rate limits, but those are not critical for a simple read tool.

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?

Three sentences, each earning its place: primary action, return contents, and batch alternative. The most important information is front-loaded, and there is no redundancy or filler.

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-resource read operation with no output schema, the description compensates by listing the returned fields and explaining embed usage. It also routes the batch case to the correct sibling. The guidance is sufficient for an agent to call the tool correctly in the common scenarios.

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 100%, so the baseline is 3. The description adds meaning beyond the schema by explaining that embed='tags,fields' fetches tags and custom fields in one round-trip, and that id is the numeric party ID. This helps an agent choose parameter values more effectively than the schema alone.

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 clearly states the operation: 'Fetch a single party (person or organisation) by its numeric id.' It also specifies the resource scope and differentiates from the batch sibling get_parties. The returned record contents are listed, leaving no ambiguity about what the tool does.

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 names the alternative for batch scenarios: 'For batch fetches of up to 50 parties at once, use get_parties instead.' It also gives practical guidance on using embed to avoid multiple round-trips, making the when-to-use context clear.

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