getJiraEntityProperty

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description adds only the 'key/value store' framing and entity coverage; it says nothing about authentication needs, error behavior when a property is absent, or what value shape is returned.

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?

A single front-loaded sentence with no wasted clauses, though it contains a small grammatical slip ('an work item') and could have used its one sentence to add usage or return-value context.

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?

There is no output schema, so the description ought to describe the returned property value, yet it does not. Combined with no usage routing and mid-level parameter coverage, the definition is adequate for a simple read but leaves the agent guessing about return shape and the entity-to-parameter mapping.

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 67%, and the schema already documents the conditional requirements for entityId, accountId, dashboardId, and issueIdOrKey. The description merely restates the entity types from the enum and adds no format or relationship detail beyond the 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?

States a specific verb (Read) and resource (property from the key/value store) and enumerates the five entity types the tool operates on, matching the entityType enum. It is clearly distinct from most siblings, though it never names editJiraEntityProperty as its write counterpart.

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 offers no when-to-use or when-not-to-use guidance and does not point to editJiraEntityProperty for modification of the same store. The entity list is scoping information, not usage guidance, leaving the agent to infer context.

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