kaiten_get_custom_property

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

No annotations are provided, so the description carries the behavioral disclosure burden. The verb 'Get' indicates a read-only operation, but the description does not disclose response format, not-found behavior, or any side effects. For such a simple getter this is minimally adequate, but it leaves some behavioral context unspecified.

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 a single, focused sentence with no filler. The key qualifier 'by ID' is present and the sentence is appropriately sized for a one-parameter getter tool.

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 tool with no output schema, the description conveys the essential call semantics: retrieve a custom property using its ID. It does not cover error cases or return structure, but these are relatively minor gaps for a tool of this complexity.

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 description coverage is 100%: property_id is already documented as an integer 'Property ID'. The description adds no further semantic meaning to the parameter, so the baseline of 3 applies.

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 names a specific verb ('Get'), a specific resource ('custom property'), and a lookup method ('by ID'), clearly distinguishing it from sibling tools like kaiten_list_custom_properties, kaiten_create_custom_property, and kaiten_delete_custom_property. The 'by ID' qualifier also signals this is a single-resource fetch rather than a list operation.

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?

There is no guidance about when to prefer this tool over alternatives. An agent must infer that it should be used when a known property_id exists, rather than using kaiten_list_custom_properties to discover properties, but the description does not state this.

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