retrieve_work_item_property

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

The description does not add behavioral context beyond what the annotations (readOnlyHint=true, openWorldHint=true) already provide. It does not mention any side effects, authorization requirements, rate limits, or output specifics. Since annotations cover the safety profile, a score of 3 is appropriate.

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 extremely concise and well-structured. It uses a clear header for the action, followed by a minimal Args list and a Returns line. Every sentence serves a purpose with no redundancy.

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?

While the description adequately explains parameters and return type, it lacks context about the nature of 'work item property' (e.g., property definition vs. property value). Given siblings like get_work_item_property_value, this omission could lead to incorrect tool selection. The presence of an output schema mitigates some completeness concerns.

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 fully compensates by explaining each parameter: work_item_property_id as UUID, project_id with scope guidance, work_item_type_id with endpoint guidance. This adds valuable semantics beyond the raw schema.

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 action 'Retrieve a work item property by ID.' It specifies the resource (work item property) and the method (retrieve by ID), making it distinct from siblings like list_work_item_properties or create_work_item_property.

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 provides some usage guidance by indicating when to omit optional parameters (e.g., 'Omit for workspace scope', 'omit to use project-level endpoint'). However, it fails to explicitly mention when to prefer this tool over alternatives such as list_work_item_properties or get_work_item_property_value, which is a notable gap.

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