decisionnode/DecisionNode

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

With no annotations provided, the description carries the full burden. It discloses specific content returned ('rationale and constraints') which hints at output structure, but lacks explicit statements about read-only safety, error handling for invalid IDs, or authentication requirements.

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?

Two efficiently structured sentences with zero waste: the first states the core operation, the second provides the workflow context. Information is front-loaded and every word serves a specific 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 lack of output schema, the description partially compensates by mentioning specific return content ('rationale and constraints'). It adequately covers the 2 parameters with 100% schema coverage and clarifies sibling relationships, though explicit error behavior would strengthen completeness.

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 schema has 100% description coverage ('Decision ID', 'workspace folder name'), and the description references the ID parameter ('by ID') but does not add syntax details, format examples, or semantic context beyond what the schema already provides. Baseline 3 is appropriate.

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-resource pattern ('Get full details of a specific decision') and explicitly distinguishes from sibling tools by referencing search_decisions in the usage workflow, clarifying this is for ID-based retrieval versus searching.

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?

Provides explicit when-to-use guidance ('Use this after search_decisions returns relevant results') establishing the tool's position in a two-step workflow (search then get details), effectively guiding the agent away from using it as a primary discovery tool.

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